You are viewing the documentation for Blueriq 15. Documentation for other versions is available in our documentation directory.
| Subject | JAVA Property | Explanation | |
|---|---|---|---|
| blueriq.security.openid-connect.roles-path | The comma-separated path to the roles claim in the JWT body. For example if the JWT body contains the following claims: {
... other claims ...
"realm_access": [
"roles": ["role1", "role2"]
]
... other claims ...
}
then this property should be set to "realm_access,roles" in order to indicate that the roles claim nested within the realm_access claim represents the user's roles. |
| |
| blueriq.security.openid-connect.teams-path | The comma-separated path to the teams claim in the JWT body. See roles-path above for an example. |
| |
| blueriq.security.openid-connect.role-mapping.<role-claim> | Maps a role claim to zero, one or multiple Blueriq roles. If a role claim does not have a mapping, it is considered to have an implicit identity mapping. Example: blueriq.security.openid-connect.role-mapping.employee=authenticated_user,vu_employee (all users which have the employee role at the identity provider will have the authenticated_user and vu_employee roles in Blueriq) |
| |
| blueriq.security.openid-connect.team-mapping.<team-claim> | Maps a team claim to zero, one or multiple Blueriq teams. If a team claim does not have a mapping, it is considered to have an implicit identity mapping. Example: blueriq.security.openid-connect.team-mapping.amsterdam=europe,netherlands (all users which have the amsterdam team at the identity provider will have the europe and netherlands teams in Blueriq) |
| |
| blueriq.security.openid-connect.username-path | The comma-separated path to the username claim in the JWT body. For example if the JWT body contains the following claims: {
... other claims ...
"realm_access": [
"nickname": "username"
]
... other claims ...
}
then this property should be set to "realm_access,nickname" in order to indicate that the Auth0 will include the claim If no value is specified, the default value is used: |
| |
blueriq.security.openid-connect.claim-mapping.<key-id>=<value> | Additional optional custom parameter to retrieve a claim from the openid-connect JWT token en place it in the Authentication. For more information see the openid connect configuration page. These claims can be retrieved to the profile using the GetAuthenticationClaims service. |
|
Overview
Content Tools