IDs & Profile
Identify is an important feature of any successful microapp. ONEm Framework makes it easy for you to identify, authenticate and manage your user state within your application. In addition, we provide a limited set of user profile data allowing you to provide a more personalized look and feel to your microapp.
When you created your microapp in the ONEm Developer Portal, you will have specified a callback path for your app to receive requests originating from users.
All requests made to the callback path contain an JWT token in the Authorization header, for example:
Your microapp can decode this token using freely available open source software to obtain details about the user and the session.
The table below details the fields that maybe included in the decoded token.
_All fields prefixed with a star (*) are always provided
|*iss||string||The issuer of the token this will be set to
|*sub||string||An id which you can use to uniquely identify the user in the ONEM ecosystem|
|*iat||number||Issued At Timestamp according to RFC7519|
|*exp||number||Token expiry timestamp according to RFC7519|
|string||User's email address|
|email_verified||boolean||Indicates if the email address has been verififed|
|name||string||User's full name|
|given_name||string||User's first name|
|family_name||string||User's family name|
|picture||string||Fully qualified path to the the user's avatar image|
|locale||string||User's language according to ISO-632-2|
|is_authenticated||boolean||Indicates if the user's session has been authenticated|
|is_authentication_supported||boolean||Indicates if user's channel supports authentication|
|is_admin||boolean||Indicates if the user making the request can be identified as the app owner|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16