Hot answers tagged ssl
2
SharePoint maintains it's own store of trusted root certificate authorities for use with it's own token service. Check out the technet blog post for more details:
http://blogs.technet.com/b/speschka/archive/2010/02/13/root-of-certificate-chain-not-trusted-error-with-claims-authentication.aspx
Open the SharePoint Management Shell to run the PowerShell ...
2
Either use the methods in this link to turn on error messages, or you should be able to log on to the physical server to see the detailed error messages.
2
A single SP farm vs virtualizing many SP farms?
A single SP farm can handle multiple SSL sites, as long as they're on unique IPs. A separate farm per site would be a waste of resources. SharePoint is designed to handle multiple.
As far as maintainable, that would depend on your site collections and content databases and anticipate database sizes. Also, ...
2
Have you done anything specificly for SharePoint performance optimization?
Object cache
In SharePoint you should adjust the object and output cache. During stress load your \SharePoint Publishing Cache\Cache hit ratio should preferably be above 90%
For object cache default is 100 mb. Adjust it up in 100 mb increments while measuring hit ratio and at the ...
2
Once you have your site in IIS, when you apply your SSL certificate to it, this applies to the entire site. Please read the instructions here: http://www.harbar.net/articles/ssl.aspx especially if you are using SSL for multiple sites. I found this to be invaluable when setting up SSL the first time with SharePoint.
2
The behavior is normal as the AAM doesn't know about your redirect, therefore the Workflow engine is not able to populate the proper Url. You should either use a Reverse'Proxy (e.g. ForeFront TMG, ISA 2006 ) that could automatically change your HTTP to HTTPS or Extend the Web Application to use HTTPS too.
Besides you can make also enable the "Configure ...
2
It could easily explainable by the concept of "Application Extension" in SharePoint, which is simply a mechanism that creates a new Web Application (it could be the same Host header too, but different Protocol, HTTP vs. HTTPS - with the purpose of offerring different authentication mechanism to different targeted people, e.g. Intranet vs. Extranet, Employees ...
2
So you're saying you've got name.net as well as name.com as SANs within your certificate?
For your canonical names you need *.name.net as a subject alternative name if you wish to use an unlimited number of canonical names.
ADFS fully supports wildcard certificates if you create them with valid subject alternative names.
2
No, this will not work if you only do that.
If you make all of the configuration changes in IIS (on all of the WFE servers) to add the new binding to the IIS site, but without telling SharePoint about it then you'll get a SharePoint monster which sometimes will kind of work. Depending on how you navigate to the first page it'll show that using the https ...
1
as ryan stated but there is a vital part missing for ssl! you need to add dns record for ssl aswell as adding the host header!
start -> admin tools -> dns
when the app loads, go into the server or add it in, expand "forward lookup zones" , expand the domain e.g. mydomain.com
if you click on the domain name, you will see to the righ some folders and files ...
1
When you have several different websites routing to the same IP/port then the only way IIS knows where they should go is using the host header (the site address)
Incoming Host Header Send to Web Application
192.168.0.1 : 80 websiteA.com A
192.168.0.1 : 80 websiteB.com B
However if you're using SSL then
The SSL certificiate is ...
1
You just have to set up the calendar sync with the appropriate web address using HTTPS. The error is telling you it's trying to connect to http://oldname.com/sites/abc/develop which isn't the URL you want configured. As a fallback, it is attempting to pull the calendar from http://prodname.com/sites/abc/develop, but that's hitting your HTTP Redirect in IIS.
...
1
Try setting the UpdateAlert in powershell.
Here is a link on the explanation http://www.wssdemo.com/Lists/stsadm/DispForm.aspx?ID=189&ContentTypeId=0x01001F9A291A8D9053488BAC958E9E294593
1
Did you configure SharePoint as the relying party in the "ADFS Account provider"? The "-realm" parameter of the SharePoint New-SPTrustedIdentityTokenIssuer cmdlet should be the identifier of SharePoint in ADFS. That is how ADFS knows who is requesting the token.
Nothing from your resource ADFS should be configured in SharePoint. It only talks with the ...
1
The sharepoint.xyz.com, from what I have gathered, is the URL you want to use. This site should have the SSL setup on it, not sharepoint2. If users are going to use sharepoint2.xyz.com securely, that'll need the SSL as well, but I think that's not the case. If it is, then you need a unique IP per site running SSL, so you'll need 2 IPs for both sites.
I ...
1
Well, at last I found out what is happening. What I didn't know is that this Datapower was terminating SSL requests and forwarding in HTTP.
The idea found here.
Off-box termination of SSL is when a proxy server terminates an SSL request and then forwards the request to a Web server by using HTTP.
I asked to the colleague that manages the Datapower and ...
1
You Fiddler session shows a connect on port 443 which is the default port for SSL yet I do not see 443 configured in SharePoint. It is also worth following up on why you are supposedly going to port 8180 in the URL but connecting to 443. This almost sounds like something is not configured right in the "black box" or that you are somehow bypassing it ...
1
Found the issue. Had to use a wildcard cert. I have multiple web apps binded to port 443. I stop the web apps sites on the server that are not needed. Looks like SharePoint doesn't care that the site is stopped or started. Still need to have a correct cert in order for the sync to work properly.
1
Have you tried removing / re-installing IIS?
You may want to disable or block remote administration tasks (admnin shares, remote-registry, etc) and see if the problem persists. If it clears up, you will want to investigate any items being pushed out to your server including scripts, GPO's, and remote commands.
Do you have any SCHannel errors in your ...
1
Certificates can only be applied at the WebApp level in IIS, and you can only assign one certificate per application.
Unless you are using a reverse proxy that will change the URL's you will need a cert that covers each URL you will be accessing with SSL enabled.
Because your URL's utilize different domain names, you can not take advantage of a wildcard ...
Only top voted, non community-wiki answers of a minimum length are eligible
