High level steps to enable SAML integration in WebUI with Microsoft Azure EntraID
search cancel

High level steps to enable SAML integration in WebUI with Microsoft Azure EntraID

book

Article ID: 432472

calendar_today

Updated On:

Products

Autosys Workload Automation

Issue/Introduction

WCC SAML integration with Microsoft Azure EntraID

Resolution

Refer to the video published by Broadcom Educate team

Here are the high level steps in this integration :

  • On EEM Server:  a keystore is created,  keyalias configured (example: wla).   
    Optional: export the above certifcate and import on to Azure side 

  • EEM configuration via EEM URL:

Relying Party Identifier: https://testurl.example.com
Service Provider Identifier:  test
Artifact Resolution URL : https://login.microsoftonline.com/####-####-###########/saml2
IDP Host:  NA
Assertion Attribute:    http://schemas.xmlsoap.org/ws/2005/05/identity/claims/username 
signing key alias:   wla

  • On Azure side, configuration: 

Entity ID (Identifier): https://testurl.example.com
Reply URL (Assertion Consumer Service URL):  https://wcc-testurl.example.com/wcc/rest/launcher/saml

Attributes:
givenname: user.givenname 
surname: user.sumname
emailaddress:  user.mail 
name:  user.userprincipalname
Sign Request + Response = Yes

Have Azure admins create a new Assertion Attribute like:
http://schemas.xmlsoap.org/ws/2005/05/identity/claims/username  ==>  user.onpremisesAMAccountName

 

  • On Azure side, WCC's SAML Signing certificate exported.    This needs to be then imported into EEM Servers'  truststore

  • In WCC configuration -> 

Relying Party Identifier: https://testurl.example.com
Service Provider Identifier:  test
IDP meta data (exported from Azure and pasted here)
Binding:  POST

 

 

 

 

Additional Information

To speak with a customer representative or a Support Engineer see Contact Support. Scroll to the bottom of the page and click on the respective region.