On the Settings tab, make sure that Advanced Control is enabled. Setting up SSO in Tresorit’s Admin Center Step 1. The Client ID can be seen under Client Credentials. Navigate to your Application, and select the General tab. The Client ID can be found under the Applications tab of your Okta Admin UI. If it’s, then your Organization ID is mycompany. You’ll only need to note the part between and. The Organization ID is your Okta subdomain. Now that the configuration is done, you will need two (if you set a custom issuer URI earlier, three) Identifiers from the Okta Admin UI. Navigate to the Security / API section, and select the Trusted Origins tab. The Granted consent table should list it as seen below. If you have one that you’d like to use, please select it here, as you’ll have to set it up in Tresorit Admin Center as well a bit later.Īt the configuration panel of your Okta Application, go to Okta API Scopes. , then you do not have a custom issuer domain. Here you can select which issuer domain you wish to use. Under the Sign on tab, you’ll be able to view the custom issuer domain at OpenID Connect ID Token editor. If you’d like to let Tresorit use this domain for redirections during login, please provide it when you enable SSO in the Admin Center. To set this URL up, please refer to Okta’s documentation about this feature. This requires additional steps from your IT infrastructure. Setting a custom issuer domain allows you to have a custom login URL as a subdomain of your company domain, like. Setting a custom issuer domain (Optional) This is required for your users to have access to this application. You can create your Group assignments here (this can be done later as well). Make sure to remember the Client ID, since it will be required later.Įnsure that the following Grant types are checked: Registering an applicationĬlick on Applications and Create App Integration, then select OIDC - OpenID Connect and select Native application, and click Next.Įnter a Name for your app (such as Tresorit).Īfter you’ve successfully created an application in the Client Credentials section, you’ll see the Client ID of the newly created application. This can be achieved by setting the attribute's Source priority to Inherit from Okta. It is required for the TresoritLoginKey to be mastered by Okta or at least modifiable through Okta's API. The Read-Write permission needs to be modified after saving the attribute on the editor screen: Click Add Attribute to add TresoritLoginKey to your user schema with Read-Write permission: Extending the user profile schemaĬlick on Directory and Profile Editor, then choose Okta from the filter list and select User (default). #Rabatt tresorit how toHow to set up SSO in Tresorit Configuring a new application in OktaĪs a first step, ensure that OAuth 2.0 for Okta APIs is enabled on the organization. Please note that If you're using SSO, Internet Explorer 11 and all versions of Microsoft Edge until 44.19041 are not supported. Once you have the GUIDs, you can set up the policy groups and users and enable SSO policy for them, as a last step. During this configuration, you will acquire GUIDs that you’ll have to set in Tresorit’s Admin Center. You’ll have to create and configure a new application on the Okta Admin UI under Applications. This documentation will guide you through setting up Tresorit SSO with Okta.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |