Okta - j5 - 28.0 - Installation & Upgrade - Hexagon

j5 Installation and Upgrade

Language
English
Product
j5
Search by Category
Installation & Upgrade
j5 Version
2019

Okta is used to authenticate users when j5 is hosted on Hexagon SmartCloud.

Authentication config - Okta

  • Authorization Provider - Select Okta

  • Authorization Provider URL - Enter the URL for the authorization server. This is provided by Okta.

  • Authorization Server ID - Enter the ID for the authorization server.

  • Custom claim for j5 username - Enter the custom claim key to retrieve the j5 username from the oAuth bearer token.

  • Custom scopes for oAuth - Enter a comma-separated list of the custom scopes used for the oAuth authentication.

  • j5 Client ID - Enter the ID for the configured application on the authorization server. This is the value generated by Okta.

  • Mapping of M2M applications and j5 users - List the client ID, corresponding auth server, audience, and j5 user mappings in a semi-colon separated list. This should be formatted as: "<client id 1>,<auth server 1>,<audience>,<j5 user 1>;<client id 2>,<auth server 2>,<audience>,<j5 user 2>"

  • OpenID Connect metadata document URL - Enter the URL for the authorization servers OpenID configuration endpoint. This field isn't required for the Okta authorization provider.

  • Use access token as oAuth bearer token - Enter the access token details in this field when Okta has been configured to return the j5 username in response to an access token instead of an id token. j5 uses an id token to retrieve the bearer token from your IdP when this field is not configured.

The bearer token needs to meet certain requirements. Refer to Bearer token requirements for more information.