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

By Ashwin Venugopal -

 

To read part 1 please click here


Azure Active Directory Integration with SAP Fiori

Benefits of integrating Azure AD with SAP Fiori:
  • You can use Azure AD to control who has access to SAP Fiori.
  • Users can be automatically signed in to SAP Fiori with their Azure AD accounts (single sign-on).
  • You can manage your accounts in one central location, the Azure portal. 

For the configuration of Azure AD with SAP Fiori, you will need the following items:

  • An Azure AD subscription.
  • A SAP Fiori subscription with single sign-on enabled.
  • SAP Fiori 7.20 or later is required.

Add SAP Fiori to Azure portal

Firstly, you have to add SAP Fiori from the SaaS application gallery to your list of managed SaaS apps, if you want to integrate Azure AD with SAP Fiori.

Configure Azure AD single sign-on

You have to perform the following tasks to configure Azure AD single sign-on with SAP Fiori:

  • Configure Azure AD single sign-on to enable your users to use this feature.
  • Configure SAP Fiori single sign-on.
  • Assign Azure AD users to the SAP Fiori application.
  • Create SAP Fiori users linked to their Azure AD user accounts.

Azure AD integration with SAP HANA

Following are the benefits offered by integrating Azure AD with SAP HANA:
  • You can control in Azure AD who has access to SAP HANA.
  • You can enable your users to be automatically signed-in to SAP HANA (Single Sign-On) with their Azure AD accounts.
  • You can manage your accounts in one central location - the Azure portal.

You will require following items if you want to configure Azure AD integration with SAP HANA:

  • An Azure AD subscription
  • A SAP HANA subscription that's single sign-on (SSO) enabled
  • A HANA instance that's running on any public IaaS, on-premises, Azure VM, or SAP large instances in Azure 
  • The XSA administration web interface, as well as HANA studio installed on the HANA instance.

It allows you to implement SAP HANA supports IDP initiated SSO and SAP HANA supports just-in-time user provisioning.

Azure AD integration with SAP NetWeaver

You enjoy following benefits after integrating Azure AD with SAP NetWeaver:
  • You can control in Azure AD who have access to SAP NetWeaver.
  • You can enable your users to be automatically signed-in to SAP NetWeaver (Single Sign-On) with their Azure AD accounts.
  • You can manage your accounts in one central location - the Azure portal.
The following items are required to configure Azure AD integration with SAP NetWeaver:
  • An Azure AD subscription 
  •  SAP NetWeaver single sign-on enabled subscription
  • SAP NetWeaver V7.20 required at least. 
SAP NetWeaver supports SP intiated SSO.

Active Directory integration with SAP Single Sign-On (Kerberos-SPNEGO)

To integrate SAP SSO with Active Directory:

  • Configure the SAP system- You have to use the configuration wizards (transactions SNCWIZARD and SPNEGO) starting with NetWeaver ABAP version 7.31 in your SAP system to configure SSO, while for the earlier versions, or if you don't have access to the configuration wizards, you have to configure SSO manually.

  • Configure user mapping:

  1. Sign in to your SAP instance via SAPGUI and run transaction SU01.
  2. Enter your SAP user (or the user that you want to map for SSO) in the name field and select Edit.
  3. Select the SNC tab and type the SNC name you configured in the previous task in the format p:CN=USERPRINCIPALNAME@DOMAIN

  • Install secure login software on client computers

  • Configure SAP GUI for SNC communication

  1. In the Secure Network Settings Interface, type the SNC Name in the format p:CN=ServicePrincipal-Name@domain
  2. Initiate a connection and you should be signed in without being prompted to enter a password.



To read part 1 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