Where is ssp admin page

At this point, the admin interface offers read access to a bunch of information, none of which is very sensitive. I can't think of any huge harm that could come from someone cracking my SSP admin password that they couldn't do without it. Yes, it might give a few vectors for DOS attacks, but honestly one could come up with ways to bog down the server and launch a similar attack without bothering to crack the password first.

This seems to me to be another case of security scanning software over-generalizing things. Yes, it's an admin URL, but it doesn't give the hacker the keys to the kingdom. I think your security folks might be making a mountain out of a mole hill, Harmen. Hi Jaime, Keith and Tim, Thanks for your answers and input! Harmen Oorspronkelijk bericht Van: simple The security of something should not depend on it being unknown or hidden. Additionally, they are kind of missing the point of SSP. The same problem applies to regular login.

An application that provides any kind of security cannot make your infrastructure secure beyond the limits of the application itself. Leave a Reply Cancel reply Enter your comment here Fill in your details below or click an icon to log in:. Email required Address never made public. Name required. RSS feed. Search for:. Use this forum to discuss topics about deployment for versions of SharePoint prior to Sign in to vote.

This used to work. However, I do not know how long ago it was that I was last in the page. What do I need to do to get that page again - and what account privs do I need to do it? So, I am trying to figure out what to try next to get that management page back. Thank you for your help. Wednesday, May 9, PM. In the qa farm, the SSP administration site is missing. Habanero Consulting Group. Tuesday, May 15, PM.

HTTP is a "bad request" which doesn't necessarily mean the site is missing. Jason Warren. Friday, May 11, PM. HI, Are you able to see application pages via ssp website? Do you have any other SSP created? If yes you can mark that as default.

I hope this will help you out. Thanks, Rahul Rashu. So, I can't tell you if it is in its own content database. Does that help any? Monday, May 14, PM. Can you describe your farm? How many servers, role of each? I'm confused by your latest post, are MyMachine and thatmachine in the same farm? Tuesday, May 15, AM. You should follow the instructions for creating a Web application as defined in Chapter 2, "Deploying SharePoint Products and Technologies," but at a minimum, the following options should be configured:.

Fill out the host header information, even if you plan to use assigned IP addresses. Security configuration If you plan to provide or consume Shared Services over untrusted networks, seriously consider using SSL for this Web application. In addition, you can use Kerberos to enhance your security posture and improve performance. Verify that the automatically inserted text is correct and make any changes as required.

If multiple administrators will access your Shared Services administration from geographically disperse locations, strongly consider using a standard port for access, such as 80 or Be careful when publishing externally, however, as inadvertently publishing your SSP administration page to the Internet could be catastrophic, should a hacker gain access.

Application pool Always create a dedicated application pool and identity for every SSP. This dedicated pool allows for isolation of the Web application and associated services, thereby improving performance and security.

Note that SSP administration can now be performed by non-farm administrators, enabling the granular delegation of tasks, such as Search and Indexing.

Recycling the application pool for your SSP, for example, does not affect the rest of your server farm's Web applications. You cannot use Network Service for this Web application and should always use an Active Directory account when possible. Database name and authentication It is possible to use a different database server than was specified for Central Administration and the configuration database, but only do so in large or specialized environments. The best practice is to use the same SQL Server installation for all databases.

You should name the database according to the purpose of the SSP, and the name should match closely the name of the IIS Web application. Figure shows an example of database naming for Contoso, Ltd. Although it is easier to simply use the SSP Web application just created, doing that makes disaster recovery more difficult. This allows for application pool isolation, troubleshooting, disaster recovery, and, most important, the ability to independently load balance your My Site Web application.

Figure is an example of the Web application settings for a dedicated My Site Web application.