If the keyUsage extension is included in the certificate, it must also have the keyCertSign bit set, as stated in RFC 5280, to work with WSS. Another possible option is to not include the key usage extension in the certificate.
Blue Coat Auth Connector
Successfully works as an IDP (IDP option must be selected during installing of the Auth Connector).
Tested and works.
Confirmed to work in multiple customer environments.
The entity ID must be unique for WSS. Currently, all WSS customers use the same entity ID of https://saml.threatpulse.net:8443/saml/saml_realm. Blue Coat plans to develop a unique entity ID for its WSS customers; this is currently targeted to be completed mid-2015 (this time frame is conditional and might change without notice).
Fails to work in one customer environment because of the minted certificate including the keyUsage extension but not including the keyCertSign bit.
Imported Document ID: 000015970
Subscribing will provide email updates when this Article is updated. Login is required.
Thanks for your feedback. Let us know if you have additional comments below. (requires login)
Subscribed to the Article.
Unable to subscribe
Thanks for your additional feedback !!!
Enterprise Support Virtual Agent
Rate Me :
Tell us more:
Welcome! My name is Sami, the Enterprise Support Virtual Agent answering technical support questions.