Integrate SAP Analytics Cloud with Okta
Enable provisioning for your SAP Analytics Cloud instance to integrate with Okta.
Before you begin
- You have an active SAP Analytics Cloud integration and an Organization Account.
- If you have a standard or trial subscription, your tenant is provisioned automatically and needs to be activated. See Activate Your Account.
- If you want to provision the app using the SAP Business Technology Platform cockpit, see Create Your SAP Analytics Cloud Instance in SAP BTP Cockpit.
- You're a system owner with admin privileges that allow you to manage users.
- You've created an OAuth app in SAP Analytics Cloud. See Set Up Third-Party Access with OAuth Clients.
- When you create the app, set the Purpose to
Interactive Usage. This setting controls the authorization code flow for when a user signs in to the app. - Use this redirect URI:
https://system-admin.okta.com/admin/app/generic/oauth20redirect.
- When you create the app, set the Purpose to
- You have Client ID, Client Secret, Token Domain, and Authorization Domain values for your OAuth client. To find these values, go to in your SAP Analytics Organization Account.
- You have a tenant domain. To find this, go to in your SAP Analytics Organization Account.
- You know which attribute your SAP Analytics Cloud tenant uses for SAML mapping. To check this, go to in your SAP Analytics Organization Account, and check the User Attribute setting in your SAML SSO configuration. This value is User ID, Email, or Custom SAML Mapping. If your tenant uses custom SAML mapping, a SAML User Mapping column appears under .
SAML user mapping
Important: This integration uses the SAP Analytics Cloud SCIM 1.1 endpoints, where the
userName is the SAML mapping property. The username value that Okta sends determines the SAML mapping for every user it provisions, and it must exactly match what your tenant is configured to use.Mapping reference
| SAP Analytics Cloud SAML mapping | Okta username format |
|---|---|
| User ID | Use the same value that SAP Analytics Cloud expects for the user ID. |
| Use the user's email address. | |
| Custom SAML Mapping | Use the custom source attribute that matches your tenant's SAML User Mapping value. |
On the app's Sign On tab, set Application username format to the same source attribute that produces your SAML NameID. If the provisioned username and the NameID don't match, users are created in SAP Analytics Cloud but can't sign in.
Add the app integration to Okta
-
In the Admin Console, go to .
- Search for and select the SAP Analytics Cloud app integration.
- On the General tab, enter the Application label and click Done.
- Click the Provisioning tab, click Configure API Integration, and select Enable API integration.
- Enter your Token Domain without the
/oauth/tokenendpoint and thehttps://extension. Your token URL uses this format:https://<tenantName>.authentication.<region>.hana.ondemand.com/oauth/token. - Enter your Authorization Domain without the
/oauth/authorizeendpoint and thehttps://extension. Your authorization URL uses this format:https://<tenantName>.authentication.<region>.hana.ondemand.com/oauth/authorize. - Enter your Tenant Domain without the
https://extension. - Enter your Client ID and Client Secret.
- Optional. Select Import Groups if you want to import user groups into Okta.
- Click Authenticate with SAP Analytics Cloud.
- Enter your SAP Analytics Cloud admin credentials.
- Click Accept.
- When the authorization process completes, click Save.
- Select To App under Settings. Click Edit, and then select the provisioning features that you want to enable.
- Click Save.
Known limitations
- If your tenant's SAML mapping is User ID, SAP Analytics Cloud doesn't allow you to change the
userNamethrough the API. Changing a user's Okta username after provisioning doesn't update the username in SAP Analytics Cloud. - SAP Analytics Cloud matches users by
userName. An existing SAP Analytics Cloud user whoseuserNamedoesn't match the Okta username isn't matched during provisioning. - If you switch your tenant to Custom SAML Mapping after users already exist, the SAML User Mapping column is empty for those users. You need to update it manually in SAP Analytics Cloud.