Implementing AD & Azure AD-based Authentication (part 1)

By Ashwin Venugopal -

 




To read part 2 please click here


SAP Cloud Platform Identity Authentication

Add SAP Cloud Platform Identity Authentication from the gallery

If you want to configure the integration of SAP Cloud Platform Identity Authentication into Azure AD, then firstly we have to add SAP Cloud Platform Identity Authentication from the Azure AD application gallery to the list of managed SaaS apps.

Implement Azure AD single sign-on

After that you have to configure and test Azure AD-based SSO with the help of following steps:
  • Configure Azure AD Single Sign-On - to enable your users to use this features.
  • Configure SAP Cloud Platform Identity Authentication Single Sign-On - to configure the Single Sign-On settings on application side.
  • Assign Azure AD users to SAP Cloud Platform Identity Authentication.

Configure Azure AD single sign-on

First of all select Single sign-on at the SAP Cloud Platform Identity Authentication application integration page in the Azure portal.

Next select SAML/WS-Fed mode to enable single sign-on.

After that, click on Edit icon open Basic SAML Configuration dialog.

On the Basic SAML Configuration section, to configure IDP initiated mode, you have to specify the SAP Cloud Platform IAS tenant identifier (Entity ID) and the corresponding Reply URL (Assertion Consumer Service URL).

To obtain these values, you can contact the SAP Cloud Platform Identity Authentication Client support team at https://cloudplatform.sap.com/capabilities/security/trustcenter.html

Configure the relevant claims for this application, including givenname, surname, emailaddress, name, and Unique User Identifier. 

Configure SAP Cloud Platform Identity Authentication Single Sign-On

Upload Azure AD metadata XML file or configure manually the following fields:
  • Name: the entity ID of the corporate identity provider.
  • Single Sign-On Endpoint URL: For Binding, choose the one that corresponds to respective single sign-on endpoint.
  • Single Logout Endpoint URL: For Binding, choose the one that corresponds to respective single logout endpoint.
  • Signing Certificate: The base64-encoded certificate used by the identity provider to digitally sign SAML protocol messages sent to Identity Authentication. 

  Assign Azure AD users

In the Azure portal, select Enterprise Applications, select All applications, and then finally select SAP Cloud Platform Identity Authentication. In tha applications list, select SAP Cloud Platform Identity Authentication.

Note- You don't have to create a user in SAP Cloud Platform Identity Authentication and the users who are in Azure AD user store can use the SSO functionality.  



To read part 2 please click here





Comments

Post a Comment

Popular posts from this blog

Deployment (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Microsoft Monitoring Agent (MMA) MMA is used across multiple Microsoft solutions and has undergone a few name changes as its features and functionality have evolved. If it is being considered to be used, then following areas should be covered during a Microsoft Sentinel deployment project: Consider the timelines and the strategy for a migration to AMA (Azure Monitor Agent) before the MMA end-of-life.  Consider the central deployment and management methodology for MMA. Determine which endpoints are in scope for deployment as these affect the log ingestion volume significantly.  Azure Monitor Agent (AMA) Organizations with MMA as the main Microsoft Sentinel agent should start planning the migration to AMA as soon as possible to avoid a rushed migration. One of the main advantages of AMA is the ability to control the log collection policy centrally and apply different policies against different groups of computers, re
Read more

Project Resourcing (Part 2)

By Ashwin Venugopal -
Image
  To read part 1, please click  here Engineering - SIEM The SIEM engineers configures Microsoft Sentinel, including Log Analytics, Logic Apps, workbooks, and playbooks. They are also responsible for the following high-level tasks: Initial configuration of Azure tenant, including provisioning required resources, assigning access roles, and configuring workspace parameters like log retention, resource tagging, and blueprints.  Deployment and configuration of syslog/CEF log collection agents in appropriate locations to collect logs from on-premises devices. Generally, it will be joint effort of both system engineer and SIEM engineer, involving configuration and potential troubleshooting.  Working with system owners to enable log forwarding and configuring any required parsing of log data in Log Analytics.  Working with security operations to create and deploy KQL analytic rules to offer detections for SOC/Computer Security Incident Response Team (CSRIT) use. Tuning of alert rule parameter
Read more

Design Planning (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Complex Organizational Structures SIEM can be an expensive security control, hence, it is common multiple businesses to contribute to the overall expense. Various organizational units may require a level of access to specific dashboards or sets of data. Microsoft Sentinel offers the ability to assign table-level permissions and limit the level of access to the minimum required to perform requisite job functions.  Role-based Access Control (RBAC) Requirements Microsoft Sentinel offers an extensive list of Azure built-in roles that can be used to provide granular access according to the job requirements and permitted level of access. Some of them are various Microsoft Sentinel dedicated roles: Microsoft Sentinel Contributor- Can perform all engineering-related configuration, such as creating alert rules, configuring data connectors, and additional similar tasks.  Microsoft Sentinel Reader- Can query the log data stor
Read more