I have a customer looking to configure a 3rd party tool that has SAML support. According to the customer, they can load in my SAML metadata and then step through a wizard to "map" the details. The Metadata generated from Okta does not contain the attributes (first, last, email) that I configured in the SAML app setup. Should it? If so, why doesn't it?
My first reaction was that the metadata only defined endpoints and certificate rather than the assertion itself.