Configuring SSO with Okta

Prerequisites

Before you start, do the following:

• Submit a ticket to SAP LeanIX Support to request setting up SSO for your organization. If you're an SAP customer, submit a request from the SAP for Me portal.
• Learn about the SSO configuration process in SSO Configuration Process.

For additional information, visit the Okta website.

Step 1: Create an Application for SSO

Follow these steps:

1. In the Okta admin dashboard, in the Applications section, click Create App Integration.

2. In the overlay that appears, select SAML 2.0 as the sign-in method.

   

3. Enter a name for your application, then click Next.

Step 2: Configure SAML Settings

Follow these steps:

1. In the SAML Settings section of the application, specify the following:

   • Single sign-on URL: https://{SUBDOMAIN}.leanix.net/Shibboleth.sso/SAML2/POST

   • Audience URI (SP Entity ID): https://{SUBDOMAIN}.leanix.net/Shibboleth.sso

     📘

     Note

     Replace {SUBDOMAIN} in the URLs with your custom subdomain that you specified in the SSO request form (for example, https://your-company.leanix.net).

   • Name ID format: Select EmailAddress.

   • Application username: This parameter depends on your Okta implementation. If the Okta username matches the SAP LeanIX email, select Okta username.

     

2. In the Attribute Statements section, specify attributes to be added to the SAML assertion as shown in the following table. All fields are case-sensitive. The first four objects in the table are values that already exist on the user object. The role object will be added when assigning user groups to the application.

   Name	Name Format	Value	Description
   firstname	URI Reference	user.firstName	The first name of the user.
   lastname	URI Reference	user.lastName	The last name of the user.
   uid	URI Reference	user.email	The unique ID of the user in the email format. We recommend using an ID that is different from the user's email address.
   mail	URI Reference	user.email	The email address of the user.
   role	URI Reference	appuser.role	The role to be assigned to the user. Possible values: ADMIN, MEMBER, or VIEWER. If you submit multiple values separated with commas, the role with the highest level of privileges is assigned. If you're managing roles within SAP LeanIX, you can omit this attribute. To learn more, see Managing User Roles with SSO.
   customerRoles	URI Reference	appuser.customRole	The custom role to be assigned to the user. Use this attribute only for custom roles, otherwise omit it. To learn more, see Custom User Roles.
   entryACI	URI Reference	appuser.entryACI	The ID of the Access Control Entity (ACE) of a Virtual Workspace. Use this attribute only when configuring access to a Virtual Workspace, otherwise omit it. To learn more, see SSO Configuration.

   

3. In the Feedback section, specify that the app is internal, then click Finish.

   

Step 3: Configure Attribute Mapping

Follow these steps:

1. On the Sign On tab of your application, select Configure profile mapping.

   

2. In the overlay that appears, click Cancel.

3. In the Attributes section, click Add Attribute.

4. Specify the attribute details.

   • Data type: Select string.

   • Display name, Variable name, and External name: Enter role to match the attribute that you added to the SAML assertion.

   • Enum: Select Define enumerated list of values and create a list of user roles that the Okta admin can select from. The values in the following table correspond to the SAP LeanIX standard roles, but you can adjust the list according to your needs.

     Display Name	Value
     ADMIN	ADMIN
     MEMBER	MEMBER
     VIEWER	VIEWER

   • Attribute type: Select Group.

     

5. Save the changes.

Step 4: Assign Users to the Application

You can assign specific users or user groups to the SSO application.

Follow these steps:

1. On the Assignments tab of the application, click Assign > Assign to Groups.

   

2. In the overlay that appears, select a user group to assign to the application.

3. In the role list, select an SAP LeanIX role to be assigned to users in this group.

   

4. Optional: If needed, modify other attributes, then save the configuration.

5. Optional: If needed, on the Sign On tab of the application, in the Sign On Policy section, specify rules for your sign-on policies, for example, multi-factor authentication.

   

To verify your SSO configuration, first, access your workspace at https://{SUBDOMAIN}.leanix.net, then navigate to the SAML session page at https://{SUBDOMAIN}.leanix.net/Shibboleth.sso/Session. The following screenshot shows a session page with a list of required user attributes that appear under Attributes.