Adobe/Okta Attributes

[Kevin Foote]

> On Jul 25, 2017, at 8:07 AM, Craig Pluchinsky <craigp at iup.edu> wrote:
> 
> We're setting up our IDP to work with Adobe, which uses Okta.  They want specific attribute names FirstName, LastName and Email.  For anyone that has set this up did you create new attributes with the custom names or use an activation condition on the encoder?  Looking for a best practice. Also it appears these attributes are needed on the Okta side to create an Okta account.  After that it doesn't matter what you release as long as the nameId contains an email.

Yea, requiring a specific name on the wire is pretty lame given that there is a standard OID for all of these attributes.

When I set these up (v2 resolver) I just added the specific encoding to the respective resolvers for those attributes. The activation condition is not a 
bad idea though. I can tell you however, that Adobe / Okta is not the only vendor who request this from my experience. Others want this 
goofiness as well which may make your activation condition a moot point eventually.

--------
thanks
 kevin.foote