AWS IAM Identity Center (successor to AWS SSO) Integration Guide for SAP Cloud Platform Neo
Introduction
This document helps you configure IAM Identity Center to facilitate single sign-on (SSO) for SAP Cloud Platform Neo using SAML.
Topics
Prerequisites
You’ll need the following to set up SSO access to SAP Cloud Platform Neo:
-
Access to the IAM Identity Center console with permissions to manage applications.
-
An SAP Cloud Platform Neo account along with an administrator account to configure SAML SSO.
-
SAP Cloud Platform Neo supports only Service Provider (SP) initiated flow.
-
A published Application on SAP Cloud Platform Neo.
Setup instructions
- On the Configure page, in the Details section, fill in the Display name and the Description(optional) of the application.
Note
We suggest that you choose a unique display name if you plan to have more than one of the same application.
-
Login to SAP Cloud Platform Cockit as an Administrator.
-
Choose Neo.
-
Click on Security, then choose Trust.
-
Click on the Local Service Provider tab, then click on Edit.
-
Insert these values:
Field | Value |
---|---|
Configuration Type | Custom |
Principal Propagation | Disabled |
Force Authentication | Disabled |
-
Click on Generate Key Pair, then choose Save.
-
Click on Get Metadata to download SAP Cloud Platform metadata file.
-
Click on the Application Identity Provider tab, then choose Add Trusted Identity Provider.
-
Download IAM Identity Center metadata file from the URL below and upload to Metadata File, by choosing Browse....
-
For Assertion Consumer Service, choose Assertion Consumer Service.
-
Click on Save.
-
Click on Attributes tab, under Assertion-Based Attributes, insert these values: Then choose Save.
Assertion Attribute | Principal Attribute |
---|---|
first_name | firstname |
last_name | lastname |
-
In the SAP Cloud Platform Neo console, click on Security, then choose Authorizations.
-
To add users, enter the email address in the User field and then assign the subaccount, application and role for the selected user.
-
Go back to the IAM Identity Center console page where you are configuring the Application.
-
Under Application metadata, choose Browse and select the Metadata downloaded in step 8.
-
Choose Save Changes.
-
Assign a user to the application in IAM Identity Center.
Verification
Use the following sections to verify the SSO integration.
Note
Ensure that the user performing the verification is logged out of both IAM Identity Center and the application before performing the steps in each section.
Verifying Service Provider Initiated SSO from SAP Cloud Platform Neo
-
Access the SAP Cloud Platform Neo Application URL.
-
On the IAM Identity Center user portal, type the credentials of a user assigned to the application in the IAM Identity Center user portal.
-
Choose Sign In.
-
On the SAP Cloud Platform Application Neo home page, verify that both SAP Cloud Platform Neo Application and IAM Identity Center are logged in with the same user.
Troubleshooting
If sign in was not successful, please see the troubleshooting steps.
Troubleshooting
Error | Issue | Solution |
---|---|---|
Other | When IAM Identity Center creates a SAML Assertion for a user, it uses the value of the 'email' field (if they are present) from the connected directory to populate the 'Email' in the SAML assertion. Many service providers expect these attributes to contain the user’s email address. By default your directory is configured to send 'windowsUPN' in both fields. | Your directory may be configured to contain the users email in the 'Email' attribute instead. If so, you may need to change this in your Connected directory settings. |
For general troubleshooting problems, please refer to Troubleshooting Guide.
User Provisioning Types
There are two user provisioning you need to aware of:
-
Preprovisioned users
Preprovisioned users, means users must already exist in the downstream SaaS application. For instance, you may need to create SaaS users with the same subject as the AD users.
-
JIT users
JIT (or Just-In-Time) users, means users do not necessarily exist in the downstream SaaS application, and will be provisioned/created/registered the first time the user federates. You may need to enable JIT option in your SaaS application for the AD domain.