DualShield consoles such as the DualShield Admin Console (DAC), DualShield Service Console (DSC) etc are SAML Service Providers (SP). By default, those SPs are secured by the DualShield's own SAML Identity Provider (IdP) , i.e. the DualShield SSO.
...
In this article, as an example. , we will use OKTA as the third-party IdP for the DualShield Service Console (DSC).
| Table of Contents |
|---|
Set up SAML application in OKTA
...
To configure OKTA as an IdP for DualShield Service Console is basicaly the same as configuring OKTA as an IdP for any other SAML applications. In OKTA, create Bellow is the guide on how to set up a SAML application , e.g. dualShield6-dsc
Configure its SAML Settings
in OKTA:
https://developer.okta.com/docs/guides/saml-application-setup/overview/
An application called "dualshield6-dsc" is created as below:
The key parameters are:
- The Assertion Consumer Service (ACS) URL
- Audience URI (EntityID)
- Signature Certificate
Those data can be extracted from your DualShield Admin Console.
Select "SSO | Service Providers" from the main menu
Click the context menu icon of "Service Console"
Select "View" in the context menu
Click "View Metadata" button to view tge SP's metadata
Click "View Certificate" button to view th3e SP's certificate
Add external Identity Provider in DualShield
In the DualShield Admin Console, select "SSO | Identity Providers"
Click "Create" button
Configure Service Provider "Service Console" in DualShield
Select "SSO | Service Providers" from the main menu
Click the context menu icon of "Service Console"
Select "Identity Providers" in the context menu
Select "okta-dsc" in the list and save it.
Sign into the DualShield Service Console
Now, if one attempt to sign into the DualShield Service Console, they will be authenticated by OKTA
