Sign up ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

I currently have a wildcard cert * with several subject alternate names. Inside the subject alternate names, there is an entry for and several other variations.

The URL of my SharePoint 2010 site is and because of that I am hearing that my wildcard cert is not valid and I need a wildcard cert for *

Does that mean that subject alternate names are not valid for ADFS/Claims/SP2010 configuration?

During my research I found this article:

It clearly says: The Subject Name of the SSL certificate must match the names used in the ADFS configuration. For example, if you specify a federation server endpoint URL as - then the subject name on the SSL certificate for that server must be “” This is a very important item and a common misconfiguration.

I didn't see any mention of subject alternate names and if they are valid.

Even more interesting is that my symptoms match up perfectly to the blog errors in my logs. (so please don't respond with instructions for enabling error logs in ADFS, I've already done that)

Could someone please shed some light on this? Are there any articles that I skipped over?

share|improve this question
It turns out that I made a huge mistake with my explanation. No wildcard cert. My CN = My SAN = and MSFT is saying that my CN needs to be –  bitterac Feb 11 '13 at 18:11

1 Answer 1

So you're saying you've got as well as as SANs within your certificate?

For your canonical names you need * 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.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.