HELP!!! Having some issues with SharePoint Foundation after implementing SSL self-signed cert to it.
I am using a SharePoint Foundation 2010 test server to test the process of implementing SSL on Foundation. I have performed the following steps according to these two articles. I diverged a little by using a self-signed cert and using Internal URL rather than a Public URL.
http://www.sharepointconfig.com/2010/03/configuring-a-sharepoint-website-to-allow-ssl-connections/
http://blogs.msdn.com/b/sowmyancs/archive/2010/02/12/how-to-enable-ssl-on-a-sharepoint-web-application.aspx
So, not sure why, but anyone can view the SharePoint site now, which before I implemented SSL only those who had permissions in the Permissions Level list could. They would be required to authenticate to even view the site.
Not sure what changed, but before I proceed further with the actual third-party SSL cert install on my production SharePoint Foundation server, I need to figure this out so it doesn't occur on it.
Server: Server 2008 R2, SQL 2005 x64 SP4, SharePoint Foundation 2010
Any ideas or suggestions to check/verify?
Thanks in advance.
http://www.sharepointconfig.com/2010/03/configuring-a-sharepoint-website-to-allow-ssl-connections/
http://blogs.msdn.com/b/sowmyancs/archive/2010/02/12/how-to-enable-ssl-on-a-sharepoint-web-application.aspx
So, not sure why, but anyone can view the SharePoint site now, which before I implemented SSL only those who had permissions in the Permissions Level list could. They would be required to authenticate to even view the site.
Not sure what changed, but before I proceed further with the actual third-party SSL cert install on my production SharePoint Foundation server, I need to figure this out so it doesn't occur on it.
Server: Server 2008 R2, SQL 2005 x64 SP4, SharePoint Foundation 2010
Any ideas or suggestions to check/verify?
Thanks in advance.
Justin Smith
In Central Admin - APplication Management - Web App Management, select your web application and up in the ribbon, click User Policy. Take a screen shot of this box and post here.
ASKER
OK, here is the screenshot.
This is the User Policy for "SharePoint - 80" web application. Using URL "http://servername/"
Say does this issue have anything to do with the unconfigured Alternate Access Mappings?
This is the User Policy for "SharePoint - 80" web application. Using URL "http://servername/"
Say does this issue have anything to do with the unconfigured Alternate Access Mappings?
I dont see the screen. I thought you said you had already configured your AAM??? Can you post a screen of that too?
ASKER
I was having issues, so I believe I removed those settings.
Hmmmm...OK. Let me reconfigure that and then retake screenshots for you.
Hmmmm...OK. Let me reconfigure that and then retake screenshots for you.
ASKER
ASKER
You will notice the account it is logged in as System Account.
Unless you are using a proxy, you should have your Public URL match your Internal. I don't think that would would cause your site to be open to everyone though. Very strange.
ASKER
How do you configure the Internal & Public URLs to match?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.