Technology Blogs by SAP
Learn how to extend and personalize SAP applications. Follow the SAP technology blog for insights into SAP BTP, ABAP, SAP Analytics Cloud, SAP HANA, and more.
cancel
Showing results for 
Search instead for 
Did you mean: 
ALLAMPRABHU
Advisor
Advisor
SSO based on Principal Propagation for SAP Asset Manager

Agenda:
Single Sign-on Authentication Types:

Single Sign-on based on Principal Propagation for SAP Asset Manager (BTP)

Principal Propagation -process Flow


Principal Propagation: Architecture Overview


 technical landscape


Principle Propagation Compatibility

In the context of the SAP Mobile Add-On, the authorization expectation is for the SAP Cloud Connector to pass the cloud user identity through principal propagation in a subject pattern that is matched to a matched alias in the back end system.

SAP uses Rule based certificate mapping


Backend user names


Set the Principal propagation.


Step1.

SAP Cloud platform authentication setup using IAS with Azure AD

Connection to Corporate Active Directory need to establish.

Prerequisite: Cloud connector is installed and connected to SCP subaccount


Cloud Connector configuration


Step 2.

Check the BTP


BTP Cockpit


click on Local Service Provider and edit & click on Get Metadata and upload in the IAS.

Step 3.

Go to IAS tenant.


IAS Home screen


Application & Add new Application.


Add Application


Give the name to the Application.

Application Display Name:

Application Home URL: keep empty.

Application Type:

Step 4.

Go to SAP BTP Cockpit

On Trust, create a Trust Management


Add identity Authentication Tenant (we have two tenant one is used for development & quality and other is used for production.

Select the trail and confirmation popup will appear.


download the metadata.

Step 5.

Go to IAS --> Application --> Bundled Applications --> where you have created the Asset manager DEV.


Define from Metadata (upload the metadata which you have downloaded.

check the SAML 2.0 Configuration and signing Certificates.

check SHA-256 and Sign assertions is oN and sign single logout message is on and require signed single logout messages.

Save


Step 6.

Steps for IAS -Azure AD

SAML 2.0 Configuration -->go to Tenant settings and under the Assertion consumer service end point you see the metadata where you can download the metadata.


Step 7:

Upload the metadata into Azure AD

To configure the integration of SAP cloud platform Identity Authentication into Azure AD, you need to add SAP Cloud Platform Identity Authentication from the gallery to your list of managed SaaS apps.

Sign into the Azure portal using either a work or school account to Microsoft account.

in the left navigation pane, select the Azure Active Directory service.

navigate to Enterprise Applications and then select App applications.

to Add new application, select New Application

in the Add from the gallery section, type SAP Cloud Platform Identity Authentication in the search box. select SAP cloud Platform Identity Authentication from results panel and then add the app.

wait a few second s while the ap is added to your tenant.

download the metadata.


 



Login to IAS and upload the metadata in IAS.

Go to Identity Authentication Service --> Corporate Identity Providers --> create --> Add identity Provider & define the Metadata.


select the Microsoft ADFS/Azure AD as the Identity Provider Type


Enable the Single Sign on button & go to conditional Authentication and select the Default identity provider.


Enable Single Sign-on


 

Set conditional Authentication.


Save

Go to BTP

Security à Trust à Add - Identity Authentication Tenant / Trusted Identity Provider

& Add-Trusted identity Provider & upload the IAS metadata which you have downloaded






Click on the Add-Trusted identity Provider & upload the IAS metadata which you have downloaded.



 

Identity Authentication Service Account Configuration


Create a group in IAS tenant for “Administrators” of Cloud Platform mobile services

Login to IAS



Go to Applications and Budled Applications (Assertion Attribuites)


 

Cloud Platform Account Configuration

 

Now, the Cloud Platform account needs to be configured to map the IAS_CPms_Admin group to a group that is granted the desired roles.

Navigate to the “Authorization Management” screen in Cloud Platform cockpit. Go to the “Groups” tab and click on “New Group”. Create a new group called “MobileServiceAdmin


Similarly create Group “MobileServiceUser” and assign the roles mentioned. This is required for Mobile app users.

SCP/BTP - Navigate to Trust Management screen, click on “Application Identity Provider” tab and click on the trusted IdP setting that represents the IAS tenant account

Login to BTP

Similarly add the Group for Mobile App user


 



Now, navigate to “Configure development & Operations Cockpit” (refer to the screen in step 5) and click on “Roles”. Create a new role “MobileServicesCockpitAdministrator” and assign it to the group “MobileServiceAdmin”.



Click on “Destinations & Permissions”. Edit the application permissions and select the role “MobileServicesCockpitAdministrator” and save.


Flow chart for Troubleshooting the issue.

4 Comments
bing_fang
Employee
Employee
0 Kudos
Please attach the ljs log of SCC which said invalid certificate. It may need the SCC team to help to check what's wrong.

Then you can use capture the network trace by using the mobile service and attach the har file and it can help to analyze this issue.
ALLAMPRABHU
Advisor
Advisor
0 Kudos
Hi Bing Fang,

Thank you for your interest in reading the blog .

I have added the flow of troubleshooting. Adding more details here may deviate from the purpose.

Regards

Allamprabhu
Krishnakumar
Product and Topic Expert
Product and Topic Expert
0 Kudos
Nice blog Prabhu,

 

I have seen Basis, Security team members struggling with these configurations in SSAM projects These steps will definitely provide guidance for many people to setup SSO with Asset Manager App
Deepti1990
Advisor
Advisor
0 Kudos
Hello Prabhu,

the blog is very informative and detailed. Thank you for sharing the insight on the SSO connectivity required in SAM.