I'm sorry if this is an uneducated question, but I'm growing a bit desperate here.
At work, we have a few customers that are still using ADFS versions prior to 2.0 which went the SAML2 route, and I'm trying to create support for WebSSO using those versions as the identity provider. I already have support for ADFS 2.0+, Shibboleth, and Okta.
I'm testing against the "adatum" account server as I've been following Microsoft's step-by-step guide to get a working setup that I can test against.
I've gotten so far that I've managed to request and receive the RequestSecurityTokenResponse payloads that ADFS delivers at my login endpoint when a user is authenticated, but I'm at a loss as of how to get basic information such as e-mail and first and last names included with it.
The only time I've managed to get anything sent in an
attributeStatement at all is when I map one of the two "Trey*AppUsers" groups created in the guide.
Enabling the identity claims
Common Name doesn't add anything, either.
I've tried to
- Create a new custom
- Create a
Custom Claim Extractionfrom the AD
Account Storefor it
- Set it to use an LDAP attribute that ought to be there (I've tried
- Create a new
Outgoing Custom Claim Mappingfor it on the
Resource PartnerI've created for my SP, but I still don't get anything out...
I don't know why, and Googling for help for these versions of ADFS is extremely difficult, made worse by the fact that I'm not used to Windows, and I most definitely am not a sysadmin :D
Assuming this is a question worthy of being answered, could someone give me a few pointers bearing in mind that I'm (obviously) fairly retarded in this area?