![]() When user enters in web browser, the request is sent to application gateway with HTTP host header .com.Pre-requisites on SSO Configuration for Public URL Also check the first part of this blog SAP on Azure: Application Gateway Web Application Firewall (WAF) v2 Setup for Internet facing SAP Fiori Apps that describes SAP Web Dispatcher parameters. But before that it is crucial to understand the architecture and flow of request before we perform the configuration.īefore you proceed reading following section, it will be beneficial if you read Using Proxies wiki from SAP. In this example, we will configure SSO with the use of SAML by enabling SAP AS ABAP system as service provider and configuring Azure Active Directory as an identify provider. The identity provider enables you to federate identities across domains for single sign-on (SSO). Now the customer wants to offload the user authentication on to an identity provider for both internal and public URLs. In first part of the blog, we discussed technical configuration of Application Gateway WAF for internet facing SAP Fiori apps. SSO using SAML & Azure Active Directory: Overview Now in this blog we will be extending the use case further, where we will configure Single Sign-On (SSO) using SAML and Azure Active Directory (AAD) for both Public and Internal communication method. In the first segment of this blog series, we had discussed in detail about Application Gateway overview and technical steps to configure Application Gateway WAF v2 for internet facing SAP Fiori apps. First Segment: SAP on Azure: Application Gateway Web Application Firewall (WAF) v2 Setup for Internet facing SAP Fiori Apps
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |