https://trustmark.nief.org/tpat/tds/icam-oidc-op-attributes/1.0/OpenID Connect OP Requirements - Attributes1.0The attribute requirements when asserting attributes/claims with an OpenId Provider.2021-06-25T00:00:00.000Zhttps://nief.org/NIEFPRIMARYNIEF Supporthelp@nief.orghttps://nief.org/This artifact is published by the National Identity Exchange Federation (NIEF). This artifact and the information contained herein is provided on an "AS IS" basis, and NIEF disclaims all warranties, express or implied, including but not limited to any warranty that the use of the information herein will not infringe any rights or any implied warranties or merchantability or fitness for a particular purpose. In addition, NIEF disclaims legal liability for any loss incurred as a result of the use or reliance on the document or the information contained herein.NIEFFederated ICAMOpenID ConnectOIDCOpenID ProviderOPAttributeClaimAttributeClaim 21".]]>Federated Identity, Credential, and Access ManagementFederated ICAMNational Identity Exchange FederationNIEFOpenID ConnectOIDCOpenID ProviderOPNIEFNIEF Technical Guidance1Valid Attribute NamesIf the attribute definition for a transmitted claim comes from a published attribute registry that is recognized by NIEF, then the "name" of the JSON name/value pair (member) MUST be the full, formal name of the intended attribute or one of the published aliases of the attribute. If the published definition of the attribute includes an alias that is an Open ID Connect defined "standard claim" , the standard claim name SHOULD be used as the attribute name.2Valid Attribute ValuesThe value of the member MUST be a JSON array containing zero or more attribute values. If the published definition of the attribute indicates that the data type of the attribute is "Boolean", then the value(s) of the attribute MUST be Boolean values in the array. Otherwise, the value(s) of the attribute MUST be encoded as string values in the array.1Valid Attribute NamesDoes the system use appropriate claim names for all attributes that it asserts in its tokens? As a guideline, the system should use standard OIDC defined claim names where appropriate for basic user information and well-defined, community endorsed claim/attribute names otherwise.Sample Claims Statement2Valid Attribute ValuesDoes the system encode all attribute/claim values as JSON arrays, and are all values other than Boolean attribute values encoded as escaped strings?Sample Claims Statement