• Home
• Integrations
• Single Sign-On Integrations
• SAP WebGUI Single Sign-On

SAP WebGUI Single Sign-On SSO

---

Single Sign-On (SSO) solution by miniOrange provides secure Single Sign-On access into SAP WebGUI using a single set of login credentials. You can log into SAP WebGUI using miniOrange credentials or Azure AD credentials or any of your existing identity providers. With miniOrange SSO services, along with SAP WebGUI you can also login into other On-Premise and Cloud Applications using your existing Identity Providers/User Store (Azure Active Directory, Okta, Ping) credentials . Follow the given setup guide to integrate header-based SSO for your SAP WebGUI account.

Prerequisites for setting up the miniOrange SSO Connector

• Create an account on miniOrange Cloud or set up the miniOrange Identity Server using this document.
• Download the miniOrange SSO Connector [Contact Us to request for the archive].

Follow the Step-by-Step Guide given below to Configure and tests SAP WebGUI Platform

1. Configure SAP WebGUI in miniOrange

• Login into miniOrange Admin Console.
• Go to Apps and click on Add Application button.



• In Choose Application Type click on the All Apps dropdown under the OAUTH/OpenID application type.



• Search for SAP WebGUI in the list, if you don't find SAP WebGUI in the list then, search for OAuth2/OpenID Connect and you can set up your application via OAuth2/OpenID Connect.



• In the Basic tab, enter the following details:

Basic Tabs	Description
Display Name	Enter the Display Name (i.e., the name for this application).
Redirect URL	Copy the Redirect-URL from SAP WebGUI Application. You will get this URL when you create an application in the SAP WebGUI admin console.
Client ID	You can find Client ID by clicking the icon as shown below.
Client Secret	You can find Client Secret by clicking the icon as shown below.
Description (Optional)	Add a description if required.
Upload App Logo (Optional)	Upload an app logo (Optional). The app will be shown in the end-user dashboard with the logo that you configure here.




• Click on Save.
• You’ll be taken to the Policies section. Click Add Policy to proceed.



• Fill in the required fields in the dialog box that appears.

  Group Name	Select the group for which you wish to add a this policy. For multiple groups, you can click here to add a multiple/separate policies for each group.
  Policy Name	You can give a name for the authentication policy.
  First Factor	Select the login method as Password and Password-less. You can enable 2-Factor Authentication (MFA), Adaptive Authentication and Force MFA On Each Login Attempt if required.




• Click Submit to add the policy.
• You’ll see it listed once added.



• You can go to the Advanced tab to change other settings, such as the expiry time for Access, JWT, and Refresh tokens.
1. Access Token Expiry: For how long the provided access token should be valid from creation. [In Hours] A new access token has to be generated after the expiry.
2. JWT Token Expiry: For how long the generated JWT token should be valid. [ In Hours ]
3. Refresh Token Expiry:For how long the generated refresh token should be valid. [In Days] You will have to generate a new refresh token after the mentioned no. of days.



• Switch to the Authentication tab.

  Primary Identity Provider	Select the default ID source from the dropdown for the application. If not selected, users will see the default login screen and can choose their own IDP. [Choose miniOrange in this case.]
  SSO FLows	Select the desired SSO flow from the dropdown, such as miniOrange as IDP, miniOrange as Broker, or miniOrange as Broker with Discovery Flow.
  Show on Enduser Dashboard	Enable this option if you want to show this app in the end-user dashboard.
  Force Authentication	If you enable this option, users will have to log in every time, even if their session already exists.
  Allowed Logout URIs	Click the Allowed Logout URIs link to add a list of post-logout redirect URIs. Users will be redirected to one of these URIs after a successful logout from miniOrange.
  Single Logout Enabled	Enable this option to send logout requests to other applications when logging out from this app.
  Sign in URL	You can include user attributes in the sign-in URL using placeholders like {{username}}, {{primaryEmail}}, {{customAttribute1}}, etc. These placeholders will be dynamically replaced with the actual user values during the IdP-initiated SSO flow. You can generate url using following attributes: username, primaryEmail, alternateEmail, fname, lname, primaryPhone and customAttribute1. The url could be like this login.com/{{username}}/?primaryEmail={{primaryEmail}} Query Parameter Format: https://<sso-url>>?username={{username}} https://<sso-url>>?username={{username}}&email={{primaryEmail}} Path Parameter Format: https://<sso-url>>/{{customAttribute1}}/{{customAttribute2}}/?username={{username}}

• Getting Required App Details / Updating App Information:
• You can edit Application by using the following steps:
• Go to the Apps.
• From the list of configured apps, locate the app you created. Click the ( ⋮ ) icon next to the app and select the Edit option.



• Click the OAuth Endpoints section in Actions menu for your app to get the Authorization, Token and User Info Endpoints.




OAuth Endpoints:

Authorization Endpoint:	https://login.xecurify.com/moas/idp/openidsso (Note: Use this endpoint only if you want to use miniorange as oauth identity server.) https://login.xecurify.com/moas/broker/login/oauth/260174 (Note: Use this endpoint only if you are configuring any Identity Provider in Identity Providers Menu and not using miniorange as IDP.)
Token Endpoint:	https://login.xecurify.com/moas/rest/oauth/token
User Info Endpoint:	https://login.xecurify.com/moas/rest/oauth/getuserinfo
Introspection Endpoint:	https://login.xecurify.com/moas/rest/oauth/introspect
Revoke Endpoint:	https://login.xecurify.com/moas/rest/oauth/revoke
OpenID Single Logout Endpoint:	https://login.xecurify.com/moas/idp/oidc/logout?post_logout_redirect_uri=






OAuth Scopes

email :	View email address of the user
profile :	View profile attributes of the user account
openid :	Retrieve JWT token for OpenID Connect




• Click on Save.

2. Configure SSO in SAP WebGUI

• Install a Web Server such as Apache Web Server so that SAP Applications are proxied through a Web Server
• Configure the proxy rules in the Web Server to forward the traffic to backend SAP Web Servers for SAP context /irj.
$ cat sap_proxy.conf ProxyPreserveHost On ProxyRequests Off ProxyPass /irj http://sap.example.com:8080/irj ProxyPassReverse /irj http://sap.example.com:8080/irj $

• Install miniOrange – SSO Client in the Web Server to protect the web resources.
• Protect the SAP URI /irj
• Stop the SAP J2EE Dispatcher and server services
• Backup SAP_Engine_Install_Dir\ume\authschemes.xml.bkp to authschemes.xml and open in a text editor to add SSO Scheme to read SSO User Token – HTTP Headers. OB_USER is the default header name for SSO header in SAP, however we recommend using MO_USER.
<authscheme-refs> <authscheme-ref name="default"> <authscheme>SSO <authscheme>uidpwdlogon </authscheme-ref> </authscheme-refs> .. .. <authscheme name="SSO"> <loginmodule> <loginModuleName> com.sap.security.core.logon.imp.HeaderVariableLoginModule </loginModuleName> <controlFlag>REQUISITE <options>Header=MO_USER </loginmodule> <priority>5 <frontEndType>2 <frontEndTarget>com.sap.portal.runtime.logon.header </authscheme>

• Enable SSO Logoff URL
  >>Administration interface >> System Administration >> System Configuration
  >> Configuration >> Direct Editing and add the logoff URLs:
ume.logoff.redirect.url=http(s)://acme.ssogen.com/ssogen/ssologout ume.logoff.redirect.silent=false

• Update HeaderVariableLoginModule with the following variable

Module Name, Flag, Options

EvaluateTicketLoginModule, SUFFICIENT, ume.configuration.active=true
HeaderVariableLoginModule, OPTIONAL, ume.configuration.active=true,Header=MO_USER
CreateTicketLoginModule, SUFFICIENT, ume.configuration.active=true
BasicPasswordLoginModule, REQUISITE,
CreateTicketLoginModule, OPTIONAL, {ume.configuration.active=true}

• Add HeaderVariableLoginModule for each application to support SSO
  Launch Visual Administrator tool >> Choose Policy Configurations >> Authentication
  Add HeaderVariableLoginModule for each application to support SSO.
• Restart the whole SAP System and SAP Applications.

3. Test SAP WebGUI SSO Configuration

• Go to SAP WebGUI app and sign in/login and you will be redirected to miniOrange Credential Section.
• Enter your miniOrange Credentials.



• You can see you have successfully implemented Single Sign-On for SAP WebGUI with miniOrange as your OAuth Server.

4. Configure Your User Directory (Optional)

miniOrange provides user authentication from various external sources, which can be Directories (like ADFS, Microsoft Active Directory, Microsoft Entra ID, OpenLDAP, Google, AWS Cognito etc), Identity Providers (like Okta, Shibboleth, Ping, OneLogin, KeyCloak), Databases (like MySQL, Maria DB, PostgreSQL) and many more. You can configure your existing directory/user store or add users in miniOrange.

• Setup miniOrange as IDP
• Setup AD as User Directory
• Setup External IDP

• To add your users in miniOrange there are 2 ways:

1. Create User in miniOrange

2. Bulk Upload Users

1. Create User in miniOrange

• Click on Users >> User List >> Add User.



• Here, fill the user details without the password and then click on the Create User button.



• After successful user creation a notification message "An end user is added successfully" will be displayed at the top of the dashboard.



• Click on Onboarding Status tab. Check the email, with the registered e-mail id and select action Send Activation Mail with Password Reset Link from Select Action dropdown list and then click on Apply button.



• Now, Open your email id. Open the mail you get from miniOrange and then click on the link to set your account password.
• On the next screen, enter the password and confirm password and then click on the Single Sign-On (SSO) reset password button.



• Now, you can log in into miniOrange account by entering your credentials.

2. Bulk Upload Users in miniOrange via Uploading CSV File.

• Navigate to Users >> User List. Click on Add User button.



• In Bulk User Registration Download sample csv format from our console and edit this csv file according to the instructions.



• To bulk upload users, choose the file make sure it is in comma separated .csv file format then click on Upload.



• After uploading the csv file successfully, you will see a success message with a link.
• Click on that link you will see list of users to send activation mail. Select users to send activation mail and click on Send Activation Mail. An activation mail will be sent to the selected users.

• Click on External Directories >> Add Directory in the left menu of the dashboard.



• Select Directory type as AD/LDAP.



• STORE LDAP CONFIGURATION IN MINIORANGE: Choose this option if you want to keep your configuration in miniOrange. If the active directory is behind a firewall, you will need to open the firewall to allow incoming requests to your AD.
• STORE LDAP CONFIGURATION ON PREMISE: Choose this option if you want to keep your configuration in your premise and only allow access to AD inside premises. You will have to download and install miniOrange gateway on your premise.




• Enter LDAP Display Name and LDAP Identifier name.
• Select Directory Type as Active Directory.
• Enter the LDAP Server URL or IP Address against the LDAP Server URL field.
• Click on the Test Connection button to verify if you have made a successful connection with your LDAP server.



• In Active Directory, go to the properties of user containers/OU's and search for the Distinguished Name attribute. The bind account should have minimum required read privileges in Active Directory to allow directory lookups. If the use case involves provisioning (such as creating, updating, or deleting users or groups), the account must also be granted appropriate write permissions.



• Enter the valid Bind account Password.
• Click on the Test Bind Account Credentials button to verify your LDAP Bind credentials for LDAP connection.



• Search Base is the location in the directory where the search for a user begins. You will get this from the same place you got your Distinguished name.



• Select a suitable Search filter from the drop-down menu. If you use User in Single Group Filter or User in Multiple Group Filter, replace the <group-dn> in the search filter with the distinguished name of the group in which your users are present. To use custom Search Filter select "Write your Custom Filter" option and customize it accordingly.



• Click on the Next button, or go to the Authentication tab.
• You can also configure following options while setting up AD. Enable Activate LDAP in order to authenticate users from AD/LDAP. Click on the Next button to add user store.




Here's the list of the attributes and what it does when we enable it. You can enable/disable accordingly.

Attribute	Description
Activate LDAP	All user authentications will be done with LDAP credentials if you Activate it
Fallback Authentication	If LDAP credentials fail then user will be authenticated through miniOrange
Enable administrator login	On enabling this, your miniOrange Administrator login authenticates using your LDAP server
Show IdP to users	If you enable this option, this IdP will be visible to users
Sync users in miniOrange	Users will be created in miniOrange after authentication with LDAP

• Click on the Next button, or go to the Provisioning tab.

User Import and Provisioning from AD

• If you want to set up provisioning, click here for detailed information. For now, we are skipping this step by clicking Skip on Provisioning.

Attributes Mapping from AD

• By default userName, firstName, lastName, email are configured. Scroll down and click on Save Configurations. To fetch additional attributes from Active Directory, enable Send Configured Attributes. On the left side, enter the name that you wish to release to the applications. On the right side, enter the attribute name from Active Directory. E.g., if you wish to fetch company attribute from Active Directory, and send it as organization to configured applications, enter the following:

  Attribute Name sent to SP = organization
  Attribute Name from IDP = company

Test Connections

• You will see a list of directories in External Directories. Go to the directory you have configured, click Select, then go to Test Connections and click on it.



• Click on Test Connection to check whether you have enter valid details. For that, it will ask for username and password.



• On Successful connection with LDAP Server, a success message is shown.

Test Attribute Mapping

• You will see a list of directories in External Directories. Go to the directory you have configured, click Select, then go to Test Attribute Mapping and click on it.



• A pop-up will appear to add the username. After clicking Test, you will see the Test Attribute Mapping Result.

Set up AD as External Directory configuration is complete.

Note: Refer our guide to setup LDAP on windows server.

miniOrange integrates with various external user sources such as directories, identity providers, and etc.

• Okta
• ADFS
• Ping
• AWS Cognito
• Many more

Not able to find your IdP or Need help setting it up?

Contact us or email us at idpsupport@xecurify.com and we'll help you setting it up in no time.

5. Adaptive Authentication with SAP WebGUI

A. Restricting access to SAP WebGUI with IP Blocking

You can use adaptive authentication with SAP WebGUI Single Sign-On (SSO) to improve the security and functionality of Single Sign-On. You can allow a IP Address in certain range for SSO or you can deny it based your requirements and you can also challenge the user to verify his authenticity. Adaptive authentication manages the user authentication bases on different factors such as Device ID, Location, Time of Access, IP Address and many more.

You can configure Adaptive Authentication with IP Blocking in following way:

• Login to Self Service Console >> Adaptive Authentication.
• Add a Policy Name for your Adaptive Authentication Policy.



• Select your Action for behavior Change and Challenge Type for user from the Action for behavior Change Section.





Action for behavior Change Options :




Attribute	Description
Allow	Allow user to authenticate and use services if Adaptive authentication condition is true.
Challenge	Challenge users with one of the three methods mentioned below for verifying user authenticity.
Deny	Deny user authentications and access to services if Adaptive authentication condition is true.




Challenge Type Options :




Attribute	Description
User second Factor	The User needs to authenticate using the second factor he has opted or assigned for such as OTP over SMS PUSH Notification OTP over Email And 12 more methods.
KBA (Knowledge-based authentication)	The System will ask user for 2 of 3 questions he has configured in his Self Service Console. Only after right answer to both questions user is allowed to proceed further.
OTP over Alternate Email	User will receive a OTP on the alternate email he has configured threw Self Service Console. Once user provides the correct OTP he is allowed to proceed further.



• Now Enable Enable IP Restriction option from the IP RESTRICTION CONFIGURATION section to configure custom IP range.



• Select the Action you want to perform if the IP address is out of the range. i.e. Allow, Challenge & Deny.
• Specify the IP Address range for which you want above setting to reflect. You can add more than one IP Address ranges by clicking on following button +.
• Scroll to the end and click on save.

B. Adaptive Authentication with Limiting number of devices.

Using Adaptive Authentication you can also restrict the number of devices the end user can access the Services on. You can allow end users to access services on a fixed no. of devices. The end users will be able to access services provided by us on this fixed no. of devices.

You can configure Adaptive Authentication with Device Restriction in following way


• Login to Self Service Console >> Adaptive Authentication.
• Add a Policy Name for your Adaptive Authentication Policy.
• Select your Action for behavior Change and Challenge Type for user from the Action for behavior Change Section.




• Scroll down to Device Configuration section and enable Allow User to Register Device option to allow users to register their devices.
• Enter the Number of Devices which are allowed to register in field next to Number of Device Registrations Allowed
• Choose Action if number of devices exceeded (This will override your setting for Action for behavior Change.)
1. Challenge: The user needs to verify himself using any of the three methods mentioned in table in step 5.1
2. Deny : Deny users access to the system
• Enable option Send email alerts to Users if number of Device registrations exceeded allowed count if you want to alert the user about no of devices exceeding the limit. Save the configuration.

C. Add Adaptive Authentication policy to SAP WebGUI.

• Login to Self Service Console >> Policies.
• Click on Edit option for predefined app policy.



• Set your application name in the Application and select password as Login Method.
• Enable Adaptive Authentication on Policy page and select the required restriction method as an option.
• From Select Login Policy dropdown select the policy we created in last step and click on save.

D.Notification and Alert Message.

This section handles the notifications and alerts related to Adaptive Authentication.It provides the following options :

• Get email alerts if users login from unknown devices or locations : Admin need to enable this option to enable receiving alerts for different alert options.
  
  
  

Option	Description
Challenge Completed and Device Registered	Enabling this option allows you to send an email alert when an end-user completes a challenge and registers a device.
Challenge Completed but Device Not Registered	Enabling this option allows you to send an email alert when an end-user completes a challenge but do not registers the device.
Challenge Failed	Enabling this option allows you to send an email alert when an end-user fails to complete the challenge.






• Next subsection is Send email alerts which allows us to enable or disable alerts for admin and end-users. To enable alerts for admins, you can enable the “Administrators” switch button.




• In case you want multiple admins accounts to receive alerts then you can enable the option for admin and then enter the admin emails separated by a ‘,’ in the input field next to Administrators email to receive alerts label. To enable alerts for the end-users, you can enable the “End Users” switch button.
• In case you want to customize the deny message that end user receive in case his authentication denied due to adaptive policy, you can do this by entering the message inside “Deny message for Adaptive Authentication” text box.


How to add a trusted Device

1. When End-user log in to the self service console after the policy for device restriction is on, he is provided the option to add the current device as a trusted device.

External References

• Single Sign-On (SSO)
• Know more about SAP SSO