SAML Single Sign-On (SSO) Configuration Guide

  • Updated on June 9, 2026

OVERVIEW

GDMS and GWN Manager support SAML (Security Assertion Markup Language) to provide external authentication and Single Sign-On (SSO) using third-party identity providers such as Microsoft Entra ID (Azure AD), AD FS, and Duo.

This guide outlines how to configure SAML information on supported third-party identity providers as well as how to use SAML SSO on GDMS (Cloud) and GWN Manager (On-Prem).

SAML COMPONENTS

When using SAML, there are two key elements:

  • Identity Provider (IdP): The authority for the user’s identity. It validates user credentials and provides identity attributes by knowing the user’s username, password, and any groups/attributes (Example: Microsoft Entra ID, AD FS, Duo).
  • Service Provider (SP): The application that the user wishes to use. In this case, the GDMS platform and GWN Manager.

SAML SSO LOGIN METHODS

SAML SSO login supports two methods:

  • Method 1: Users authenticate directly from a third-party identity provider portal (such as Entra MyApps or Duo Dashboard) and are redirected to the platform.
  • Method 2: Users access the GDMS or GWN Manager login page directly and are redirected to the configured SAML identity provider for authentication.

SAML SSO WITH MICROSOFT ENTRA ID

Firstly, users need to sign up for an Azure account by visiting this web page:

https://www.microsoft.com/en-us/security/business/identity-access/microsoft-entra-permissions-management

This section mainly introduces how to configure Microsoft Entra ID (formerly known as Azure AD) as the identity provider (IdP) for GDMS.

Step 1: Add a new application in Azure

  1. Sign in to the Microsoft Entra admin center as a Cloud Application Administrator or higher.
  2. Go to Identity Applications Enterprise applications New application.
Add a New Application
  1. In the Browse Microsoft Entra Gallery section, click Create your own application.
  1. Enter your application name, such as “GDMS”, and select “Integrate any other application you don’t find in the gallery (Non-gallery)“.
Creating an Application in Azure
  1. Click Create to successfully create the application. You can view the application in the list.

Step 2: Create an application role in Azure

  1. Sign in to the Microsoft Entra admin center, go to Identity → Applications → APP registrations, and click on the app you have created.
Azure App Registrations Page
  1. Click APP roles on the left, and then click Create app role. Then fill in the display name, select “Both” for type, and the Value must be consistent with the SAML role value expected by the Service Provider, such as “Admin.A“.
Create an App Role
  1. After successful creation, you can see this role in the list.
List of App Roles

Step 3: Add users to the application in Azure

  1. Sign in to the Microsoft Entra admin center, go to Identity Applications Enterprise applications, find and select the app you created in the application list.
  2. Then, click Users and groups on the left bar and select Add user/group.
Add UserGroup to an App
  1. Select the users you want to assign to use this app.
App User Selection
  1. Select Assigned Roles and choose from the application roles you just created.
Assigning Roles to App Users
  1. Then click Assign. After the assignment is successful, you can see the selected users and the assigned roles in the list. (These users can then log in to GDMS/GWN Manager with a single sign-on)
List of App Assigned Users

Step 4: Set up SSO in Azure

  1. Sign in to the Microsoft Entra admin center, go to Identity Applications Enterprise applications, find and click the app you have previously created.
  2. Click Single Sign-on on the left and click SAML on the page.
App SAML SSO Page
  1. First, within the Basic SAML Configuration section, click Edit.
App Basic SAML Configuration
  1. Copy the information from the GDMS/GWN platform and fill in the following information:

Identifier (Entity ID)

Fill in the Entity ID displayed on the SAML SSO page in Users (as shown in the picture, click one-click copy)

Reply URL

Fill in the ACS URL displayed on the SAML SSO page in Users (as shown in the figure, click one-click copy)

Relay State

Specify the Service Provider URL that users should be redirected to after successful authentication.

  • For GDMS, enter: https://www.gdms.cloud

  • For GWN Manager, enter the access URL, which may be either: https://<gwn-manager-domain>:<port> or https://<gwn-manager-ip>:<port>

Note: Although this field appears optional, it is required for this integration. You must configure it to prevent user errors.

GDMS SAML SSO Configuration Page
GWN Manager SAML SSO Configuration Page
Copying the Entity ID and ACS URL to Entra ID
  1. Then, within the Attributes & Claims sectionclick Edit.
SAML Attributes Claims Section
  1. Click Add new Claim.
Add a New Claim
  1. Add the following SAML claims in Microsoft Entra ID. The claim names (URIs) must match the requirements of the target platform.

Claim

Name

Source attribute

GDMS

Claim 1 (Role)

user.assignedroles

Claim 2 (Email)

  • Primary: user.userprincipalname

  • Fallback: user.mail

Claim 3 (Other Email)

user.mail

GWN Manager

Claim 1 (Role)

user.assignedroles

Claim 2 (Email)

  • Primary: user.userprincipalname

  • Fallback: user.mail

Claim 3 (Other Email)

user.mail

SAML Claim Configuration
Note:

For Entra ID integrations, it is recommended that the Email claim must be set to user.userprincipalname. When using user.mail instead, please ensure that the Contact Email field is populated to avoid any SSO failures.

Entra User Properties
  1. Download the metadata file for configuration on GDMS.
SAML XML Metadata

Step 5: SAML SSO in GDMS/GWN Manager

  1. Download the metadata of the GDMS application you created from Azure.
Downloading the SAML Metadata File
  1. Log in to the GDMS or GWN Manager platform as a super administrator and navigate to Users→SAML SSO.
Note:

Only the super administrator account has the permission to configure SAML SSO.

  1. To configure the identity provider, click “Add SAML IdP” and fill in the information:
Adding SAML IdP in GDMS

SAML SSO

Enable or disable. If disabled, users will no longer be able to use the configured SSO authentication to log in.

SSO Access Code

Used to enter this SSO Access Code on the GDMS/GWN Manager login page, and can log in through this IdP service authentication.

Remarks

Enter your remarks.

Metadata

Upload the “Federation Metadata XML” file downloaded from Azure.

  1. After adding the IdP, configure the SAML SSO role as described in section [SAML SSO ROLES IN GDMS/GWN MANAGER]. The Role Name must exactly match the role value sent by the IdP.

SAML SSO WITH ADFS

This section describes how to configure AD FS as the Identity Provider for GDMS Cloud and GWN Manager. For more configuration instructions on ADFS, refer to Microsoft’s deployment guide.

Note:

The steps in this article only cover examples of necessary configurations. The exact implementation may vary depending on the environment, Active Directory implementation, and Windows Server updates. However, the NameID, Email Address, and Role attributes described below must be provided in the SAML assertion/token.

Step 1: Add Relying Party Trust in ADFS

  1. Open the AD FS management console via Server ManagerToolsAD FS Management.
Active Directory FS Management
  1. Click on the top-level folder (AD FS) and click Add Relying Party Trust from the Actions menu.
Add Relying Party Trust
  1. Click Start to launch the wizard.
Add Relying Party Trust Wizard
  1. Choose to Enter data about the relying party manually. Then click Next.
Selecting Data Source
  1. Enter a Display name, such as “GDMS” or “GWN Manager”, which will be displayed in the management console and to users connecting to GDMS. Then click Next.
Choosing a Display Name
  1. Click Next to skip the step of Configure Certificate.
  2. Enable Support for the SAML 2.0 WebSSO protocol.
Replying party SAML 20 SSO
  1. Enter the Relying Party SAML 2.0 SSO service URL (ACS URL), which can be copied from:
    • GDMS: Users→SAML SSO
    • GWN Manager: Organization→Users→SAML SSO
ACS URL GDMS SAML SSO
  1. For the Relying party trust identifier, fill in the Entity ID displayed on the corresponding SAML SSO (as shown in the figure, click one-click copy). Then click Add and Next.
Relying Party Trust Identifier
  1. Select the default issuance authorization rule based on your preferred security behavior. For this example, select Permit everyone. Then click Next.
Choosing Access Control Policy
  1. Review your settings and complete the wizard.
Reviewing Settings
  1. Ensure Configure claim issuance policy for this application is checked.
Relying Party Trust Added

Step 2: Set NameID Attribute in ADFS

  1. Select the Relying Party Trusts you created and click “Edit Claim Issuance Policy” on the right.
Edit Claim Issuance Policy
  1. In the Edit Claim Rules dialog, click Add Rule.
Add Rule
  1. For the Claim rule template, choose to Transform an Incoming Claim. Then click Next.
  1. Fill in the Claim rule name, Incoming claim type, Outgoing name ID Format, and select Pass Through all claim values as shown in the following screenshot. Then click Finish.
Configuring Claim Rule

Step 3: Set Email Address Attribute in ADFS

  1. Select the Relying Party Trusts you created and click “Edit Claim Issuance Policy” on the right.
Edit Claim Issuance Policy
  1. In the Edit Claim Rules dialog, click Add Rule.
Add Rule
  1. For the Claim rule template, choose to Send LDAP Attributes as Claims. Then click Next.
Claim Rule Template Send LDAP Attributes as Claims
  1. Fill in the following information and click Finish.

Claim Rule Name

Enter a name, such as “emailaddress”.

Attribute Store

Select Active Directory

LDAP Attribute

Select User-Principal-Name

Outgoing Claim Type

Enter the following based on the service provider:

Note: If GWN Manager is not bound to port 443, the port number must be included in the URI.

Mapping of LDAP Attributes

Step 4: Set Role Attribute in ADFS

  1. In the Edit Claim Rules dialog, click Add Rule.
Add Rule
  1. For the Claim rule template, choose to Send Group Membership as a Claim.
  1. Fill in the following information and click Finish.

Claim Rule Name

Enter a name, such as “role”.

User’s Group

Select the AD user group that will use this Relying Party Trust.

Outgoing Claim Type

Enter the following based on the service provider:

Note: If GWN Manager is not bound to port 443, the port number must be included in the URI.

Outgoing Claim Value

The value of the role must be the same as the SAML SSO role name configured on GDMS or GWN Manager, such as “Admin.A”.

Claim Rule Template Send Group Membership a Claim

Step 5: Configure Single Logout (Optional)

This step describes how to configure SAML Single Logout for GDMS Cloud and GWN Manager when using AD FS as the Identity Provider.

If SAML Single Logout is not configured correctly, users will encounter errors when selecting “Logout from both application and SSO system”.

GDMS Logout Prompt

The following AD FS configuration is required for both GDMS and GWN Manager:

  1. Open AD FS Management.
  2. Navigate to Relying Party Trusts and right-click the relevant Relying Party Trust (GDMS or GWN Manager) and select Properties.
Relying Party Trusts Properties
  1. Open the Endpoints tab and click Add SAML.
Relying Party Trusts Endpoints Tab
  1. Configure the endpoint as follows:

Field

Value

Endpoint Type

SAML Logout

Binding

POST

Trusted URL

Dialog for adding a SAML Logout endpoint: Trusted URL shows https://www.gdms.cloud/app/saml/logout; Response URL field is empty (examples shown below).
Trusted URL Configuration

Step 6: Configure Token-Signing Certificate

  1. In the management console, go to AD FSServiceCertificates. Select a valid certificate under Token-signing.
Certificates Page
  1. Double-click on the certificate under Token-signing. Under DetailsThumbprint, copy this string and paste it into the X.509 cert SHA1 fingerprint field in GDMS/GWN Manager.
Certificate Details

Step 7: SAML SSO in GDMS/GWN Manager

  1. The super administrator logs in to the GDMS platform and goes to UsersSAML SSO.
  2. Click Add SAML IdP and fill in the information:
Note:

Since both GDMS and GWN Manager support metadata import, administrators can upload the downloaded XML file to automatically populate the IdP configuration fields. To download the metadata, open a browser and go to: https://<adfs-domain>/FederationMetadata/2007-06/FederationMetadata.xml

Replace <adfs-domain> with the fully qualified domain name of the AD FS server.

GDMS SAML IdP Configuration Page

SAML SSO

Enable or disable. If disabled, users will no longer be able to use the configured SSO authentication to log in.

SSO Access Code

Used to enter this SSO Access Code on the GDMS/GWN Manager login page, and can log in through this IdP service authentication.

Remarks

Enter your remarks.

IdP Entity ID

Must exactly match the ADFS Federation Service Identifier, as advertised in ADFS metadata.


By default, ADFS uses:

http://<FederationServiceName>/adfs/services/trust


Note: This value is a logical identifier and does not need to be publicly reachable. It is recommended to Import ADFS metadata instead of manually entering this value.

X.509 cert SHA1 fingerprint

Fill in the Thumbprint value under the Details of the certificate in ADFS→Certificates→Token-singing

SSO Login URL

URL address for login authentication, fill in:

https://<ADFS_server>/adfs/ls/

Replace “<ADFS_server>” with the IP address or DNS name of your AD FS server.

SSO Logout URL

When logging out of GDMS/GWN Manager, you can log out of the ADFS redirection address at the same time. Fill in the following information based on the platform:

  • GDMS: https://<ADFS_server>/adfs/ls?wa=wsignout1.0&

  • GWN Manager: https://<ADFS_server>/adfs/ls?wa=wsignout1.0&

Replace “<ADFS_server>” with the IP address or DNS name of your AD FS server.

  1. After adding the IdP, configure the SAML SSO role as described in section [SAML SSO ROLES IN GDMS/GWN MANAGER]. The Role Name must exactly match the role value sent by the IdP.

SAML SSO WITH DUO

Users will have to set up a DUO account first by using this link: https://signup.duo.com/

This section describes how to configure DUO SSO as a SAML Identity Provider for GDMS or GWN Manager.

Duo Single Sign-On is a cloud-hosted SAML 2.0 Identity Provider (IdP) and OpenID Connect Provider (OP) that enables centralized authentication with multi-factor authentication (MFA) and access policy enforcement. Duo can integrate with upstream identity providers such as Microsoft Entra ID, allowing organizations to combine enterprise identity management with Duo MFA.

For details, please refer to the DUO manual: https://duo.com/docs/sso

The screenshots in this section use GWN Manager as the Service Provider (SP). The configuration steps for GDMS are identical except for the SAML attribute URLs used in the Duo application configuration.

Prerequisite (GWN Manager Only)

When using Duo SAML SSO with GWN Manager, the system clock on the GWN Manager host must be synchronized. If the system time is not synchronized, SAML assertion validation may fail, resulting in erros during login.

On the GWN Manager host, run the following commands to enable NTP and verify that the system clock is synchronized:

# sudo timedatectl set-ntp on
# timedatectl | grep “System clock synchronized”

If the configuration is correct, the output should show: System clock synchronized: yes

Step 1: Create a DUO Authentication Source

  1. Log in to the Duo Admin Panel and navigate to Applications→SSO Settings.
  2. Click Add source in the External Authentication Sources tab.
Add DUO External Authentication Source
  1. Click Add SAML Identity Provider.
Add SAML Identity Provider
  1. This page contains the values that will be used when configuring the upstream identity provider (for example, Microsoft Entra ID).
DUO SAML Identity Provider Configuration

Step 2: Configure the Azure Application

In this deployment model, Entra ID authenticates the user and sends the identity assertion to Duo, which then acts as the IdP for GDMS/GWN Manager.

Please refer to the first section of the guide for more information on configuring an App on Entra ID.

  1. Add a new application in Azure.
  2. Add users to the application in Azure.
Note:

The Azure user’s email address must be the same as the DUO user’s email address.

  1. Go to IdentityApplicationsEnterprise applications, find and click the DUO application you created in the application list.
  2. Click Single Sign-on on the left and click SAML on the page.
SSO Page for DUO Entra App
  1. Within the Basic SAML Configuration section, click Edit, and configure the following values using the information obtained from Duo.

Identifier (Entity ID)

Duo Entity ID

Reply URL (ACS URL)

Duo ACS URL

Edit DUO Entra App Basic SAML Configuration
Copying the Entity ID and ACS URL from DUO
Pasting the Entity ID and ACS URL on the DUO Entra App
  1. Within the Attributes & Claims section, click Edit, then click Add new claim. Configure the claim as follows:

Name

Source Attribute

Email

user.userprincipalname

Note:

For all Duo SAML integrations using Microsoft Entra ID as the upstream IdP, configure the Email claim to use user.userprincipalname. This avoids dependency on optional Entra ID contact fields and ensures reliable SSO for all users.

  1. From the SAML Signing Certificate section, download the Federation Metadata XML or copy the following values:
    • Login URL
    • Microsoft Entra Identifier
    • Logout URL
    • Certificate (Base64)
Copying Entra ID URLs and Downloading SAML Certificate

Step 3: Configure Single Sign-On in DUO

  1. Log in to the Duo Admin Panel and navigate to Single Sign-On.
DUO External Authentication Sources Page
  1. Select the resource you created in Step 1 (SAML Identity Provider).
  2. Enter the information copied from Entra ID:

IdP Entity ID

Microsoft Entra Identifier

Single Sign-On URL

Entra Login URL

Single logout URL

Entra Logout URL

Certificate

Upload Entra app Base64 certificate

Pasting Entra URLs and Uploading SAML Certificate
  1. Click Save, and verify that the status of the external source appears as “Enabled“.
External Authentication Source Status

Step 4: Create Users and Groups in DUO

This section describes how to create Duo users and groups for this integration.

  1. Log in to the Duo Admin Panel
  2. Navigate to Users→Add User
Add New DUO User
  1. Fill in the following fields:

Field

Value

Username

Must match the local part of the Entra ID UPN (value before @)



Email Address

Must match the full Entra ID UPN

Example:

If the Entra ID user UPN is “test@entra.com“. Configure the Duo user as:

  • Username: test
  • Email Address: test@entra.com

  1. After creating the user, complete enrollment using any supported method:
    • Email enrollment
    • Enrollment code
    • Device enrollment
Note:

The enrollment method does not affect SAML attribute matching.

DUO User Enrollment Options
  1. Navigate to groups Users→Groups and click “Add Group”.
Add DUO User Group
  1. Choose a name for the user group and add an optional description.
Configure DUO User Group Name
  1. Click on “Add users to group” to configure users allowed to access GDMS/GWN Manager.
Adding Users to DUO Group

Step 5: Create the DUO SAML Application

  1. Log in to the Duo Admin Panel and navigate to ApplicationApplication Catalog.
  2. Search for Generic SAML Service Provider.
Generic SAML Service Provider Application
  1. Configure the application name (example: GWN Manager or GDMS).
  2. Enable access for all users or select a specific group to grant application access.
Application Name and User Access Control
  1. Configure the Entity ID and ACS URL by copying them from GDMS/GWN Manager, as shown below:
GWN Manager Entity ID and ACS URL
GDMS Entity ID and ACS URL
  1. Scroll down to continue the configuration. The following three parameters are mandatory and must be configured.

NameID attribute

Select <Email Address>

Map attributes

IdP Attribute

Select <Email Address>

SAML Response Attribute

Fill in the fixed parameters for:

Note: If GWN Manager is not bound to port 443, the port number must be included in the URI.

Role attributes

Attribute name

Fill in the fixed parameters for:

Note: If GWN Manager is not bound to port 443, the port number must be included in the URI.

Service Provider’s Role

Fill in the role value, which must be the same as the SAML SSO Role name in Users→SAML SSO Role, such as “Admin.A”

Duo Groups

Select the user group to use. Only users who belong to the selected Duo group will be allowed to authenticate using SAML SSO. User groups in Duo can be created and managed under Users→Groups in the Duo Admin Panel.

GWN Manager App Attribute Mapping
  1. To enable IdP-initiated login from the Duo dashboard, configure the Default Relay State to point to the GDMS or GWN Manager login page.
DUO App Default Relay State

Step 6: SAML SSO in GDMS/GWN Manager

  1. Log in to the Duo Admin Panel and navigate to the GDMS/GWN Manager Application.
Duo Admin Panel GWN Manager Application
  1. Access the application you created, and copy the following information or download the metadata.
GWN Manager Application Metadata
  1. Log in to GDMS or GWN Manager using a Super Administrator account.
  2. Navigate to Users→SAML SSO.
Adding SAML IdP in GWN Manager
Adding SAML IdP in GDMS
  1. Click Add SAML IdP and fill in the information:

SAML SSO

Enable or disable. If disabled, users will no longer be able to use the configured SSO authentication to log in.

SSO Access Code

Used to enter this SSO Access Code on the GDMS/GWN Manager login page, and can log in through this IdP service authentication.

Remarks

Enter your remarks

Metadata

  • Method 1: Click to upload the metadata XML file to parse the fields below.

  • Method 2: Manually fill in the fields as follows.

IdP Entity ID

Fill in the Entity ID of the Metadata module in Duo→Application.

X.509 cert SHA1 fingerprint

Fill in the SHA-1 Fingerprint of the Metadata module in Duo→Application.

SSO Login URL

Fill in the Single Sign-on URL of the Metadata module in Duo→Application.

SSO Logout URL

(Optional) Fill in the Single Sign-out URL of the Metadata module in Duo→Application.

  1. After adding the IdP, configure the SAML SSO role as described in section [SAML SSO ROLES IN GDMS/GWN MANAGER]. The Role Name must exactly match the role value sent by the IdP.

SAML SSO ROLES IN GDMS/GWN MANAGER

GDMS Role Configuration

  1. Log in as Super administrator logs in to GDMS and goes to Users→SAML SSO→SAML SSO Role.
Adding SAML SSO Role in GDMS
  1. Click Add Role and fill in the following information:
Editing SAML SSO Role

Role Name

Enter the name of this role.

Note: It must be the same as the value of the application role created in Azure. For example “Admin.A”.

UC Organization

(Optional) Assigned to the Unified Communications organizations that this role can manage.

Networking

(Optional) Assign networkings that this role can manage.

  1. Click Next to configure the permissions for the GDMS UC system. If this role does not have permissions for the GDMS UC system, you do not need to select any permissions.
Configuring UC Permissions for SAML SSO Role
  1. Click Next to configure the permissions for the GDMS Networking system.
  • If you select Platform Administrator, you must select Manage All Networking in the previous step, otherwise you cannot select Platform Administrator.
  • If this role has permissions for the GDMS Networking system, you can select “None”.
Configuring Networking Permissions for SAML SSO Role
  1. Click Finish to successfully create the SSO role.
Created SAML SSO Role

GWN Manager Role Configuration

  1. Log in to GWN Manager using a local administrator account.
  2. Navigate to Organization→Users→SAML SSO.
  3. Select the SAML SSO Role tab.
GWN Manager SAML Role Page
  1. Click Add to create a new SAML SSO role.
Add GWN Manager SAML Role
  1. Enter the name of the SAML SSO role. This value must exactly match the role value sent by the IdP in the SAML assertion.
Note:

If the role name does not match exactly, GWN Manager will reject the login even if authentication is successful.

  1. After defining the Role Name, configure the permissions associated with this role. Each option corresponds to a predefined permission scope within GWN Manager.
  2. If Custom is selected, granular permissions can be assigned manually.
SAML Role Permissions
GWN Manager User Roles
  1. Click Save to complete role creation. The newly created role will appear in the SAML SSO Role list.
GWN Manager Role List

SAML SSO TESTING AND VALIDATION

This section describes how to validate SAML SSO authentication and logout behavior when GDMS or GWN Manager is integrated with an Identity Provider.

Testing should verify both authentication flows:

  • SP-initiated login: authentication starts from the GDMS or GWN Manager.
  • IdP-initiated login: authentication starts from the Identity Provider portal (Entra ID, Duo).

SP-Initiated Login Test

Web Login Test

This test verifies authentication initiated from GDMS or GWN Manager.

  1. Open a web browser.
  2. Navigate to:
    • GDMS: https://www.gdms.cloud
    • GWN Manager: https://<gwn-manager>:<port>
  3. Click Sign in with SSO at the bottom of the GDMS/GWN Manager login page.
GWN Manager Login Page
  1. Enter the SSO Access Code configured by the administrator.
GDMS SSO Access Code Prompt
GWN Manager SSO Access Code Prompt
  1. The SSO Access Code from the GDMS/GWN Manager can be configured on the SAML SSO page as follows:
SSO Access Code Configuration
  1. The browser must redirect to the configured IdP login page:
    • Microsoft Entra ID login page
    • AD FS login page
    • Duo authentication page
Microsoft Entra ID login page
AD Login Page
Duo Authentication Page
Note:

For GWN Manager, if login fails with an HTTP 500 error, verify that the GWN Manager system time is synchronized.

  1. After successful authentication, verify that:
    • You are redirected back to the application
    • Login completes successfully
    • The correct SAML SSO role is applied
GDMS Login Example with AD User
GWN Manager Login Example with Microsoft User
  1. (Optional) If SAML Single Logout (SLO) is configured, click Logout from both the application and the SSO system.
GDMSGWN Manager Logout Prompt
  1. Verify that:
    • The GDMS/GWN Manager session is terminated
    • The SSO system is terminated
Microsoft Logout Page
AD Logout Page
DUO Logout Page

Mobile App Login Test

  1. Click Sign in with SSO at the bottom of the GDMS login page, and then enter the SSO Access Code configured by the administrator.
GDMS App Login
  1. Go to the configured IdP service provider authentication page, such as Microsoft Azure, ADFS, and DUO.
Microsoft Authentication Page
  1. After authentication, log in to the GDMS APP with the corresponding SAML SSO role.

IdP-Initiated Login Test

This test verifies authentication initiated directly from the Identity Provider portal.

In IdP-initiated authentication, the IdP generates the SAML assertion and redirects the user to the Service Provider without first accessing the GDMS or GWN Manager login page.

Important:

For IdP-initiated login to function correctly, the Default Relay State (or Relay State URL) must be configured in the IdP. This value must point to the base URL of the Service Provider (for example, https://www.gdms.cloud or https://<gwn-manager-domain>:<port>). Before testing, ensure the Relay State has been configured as described in the relevant IdP configuration section.

Microsoft Entra ID

SAML SSO can be validated from Microsoft Entra ID using either:

  • The Application Test option
  • The Microsoft MyApps portal
Access using the Application Test Option
  1. Log in to the Microsoft Entra Admin Center.
  2. Navigate to Enterprise applications and select the configured GDMS/GWN application.
  3. Go to Single Sign-on→SAML.
  4. Click Test this application.
Testing Microsoft Entra ID Application

If the configuration is correct, the authentication completes successfully, and the browser redirects to GDMS or GWN Manager

Access from Microsoft MyApps Portal
  1. Open Microsoft MyApps.
  2. Sign in using an Entra ID account with permission to access the GDMS/GWN application.
  3. Click the configured GDMS/GWN application tile.
  4. Authenticate if prompted, and verify successful redirection and correct role assignment.
Application Dashboard

For more information about the My Apps, see Introduction to Microsoft My Apps.

AD FS

Before testing, verify that the IdP-initiated sign-on page is enabled on the AD FS server. Open PowerShell as Administrator and run:

Get-AdfsProperties | Select-Object EnableIdpInitiatedSignonPage

If the output shows “False”, enable it:

Set-AdfsProperties -EnableIdpInitiatedSignonPage $true
PowerShell output showing EnableIdInitiatedSignonPage = False in an Administrator session.
EnableIdpInitiatedSignonPage Output Shows False

Run the check command again to confirm the value now shows “True”.

PowerShell session showing enablement of IdInitiatedSignonPage: initially False, then set to True with output True in the console.
EnableIdpInitiatedSignonPage Output Shows True
Access via AD FS IdP Sign-On Page
  1. Open a browser and navigate to:
https://<adfs-server>/adfs/ls/idpinitiatedsignon.aspx
  1. From the application dropdown, select the configured application (GDMS or GWN Manager).
AD FS sign-in page: blue left panel, white right panel with 'Lab AD FS' and a site sign-in dropdown set to 'GWN Manager' with a Sign in button.
AD FS IdP Sign On Page Target Application
  1. Sign in using a domain user account that is a member of the AD group mapped to the GDMS or GWN Manager SAML SSO role.
Lab AD FS sign-in screen with username and password fields and a Sign in button on a white panel with a blue left background edge.
AD FS IdP Sign On Page Domain User Credentials
  1. After successful authentication, verify that:
    • The browser redirects to GDMS or GWN Manager automatically
    • Login completes without prompting for the SSO Access Code
    • The correct SAML SSO role is applied to the session
GWN Manager dashboard with Default Network overview and tiles for Router, Switch, AP, Wireless Bridge, and Clients; left navigation panel visible.
Successful IdP Initiated Login with AD FS User

DUO

When Duo is configured as the SAML Identity Provider, IdP-initiated login can be performed using Duo Central or through the upstream identity provider (for example, Microsoft Entra ID).

Unlike Microsoft Entra ID, Duo does not automatically create a user application tile for SAML applications. Administrators must manually add the application to Duo Central.

Access via Duo Central
  1. Log in to the Duo Admin Panel.
  2. Navigate to Applications→Duo Central.
  3. Ensure the Status is set to Online. If Duo Central is Offline, tiles will not be available.
DUO Central Status
  1. Click Add tile.
  2. Select Add application tile.
Adding Application Tile on DUO
  1. Locate the configured SAML application (for example, GDMS or GWN Manager).
  2. Select the checkbox next to the application.
  3. Click Add Tile.
Adding Tile for GWN Manager Application on DUO
  1. The application will now appear in the Duo Central Tiles list. Confirm the application tile shows Enabled only for permitted groups, or Available to all users.
User Access Permission or GWN Manager App

Once the tile has been successfully configured, users can follow these steps to log in from DUO Central:

  1. Open a browser and navigate to the Duo Central portal:
https://<your-subdomain>.sso.duosecurity.com
  1. Sign in using a user account with access to the configured SAML application.
  2. After login, the application tile will be displayed.
GWN Manager Tile Duo Central
  1. Click the application tile to initiate IdP-initiated SAML authentication.
  2. Enter valid credentials and complete Duo MFA verification if required.
  1. After successful authentication, you will be redirected to the configured GDMS or GWN Manager and logged in automatically.
GWN Manager Successful Login from Duo
Access via Upstream IdP (Entra ID)

When Duo uses Microsoft Entra ID as the upstream identity provider, users may also initiate login from Microsoft MyApps.

For IdP-initiated login to work correctly in this scenario, the Sign-on URL must be configured in the Entra ID application.

  1. Log in to the Duo Admin Panel.
  2. Open the configured SAML application and copy the Single Sign-On URL from the application metadata.
  1. Log in to the Microsoft Entra Admin Center.
  2. Navigate to the Duo application created earlier.
  3. Under Basic SAML Configuration, paste the copied URL into the Sign-on URL field.
  1. Open Microsoft MyApps, and sign in using the Microsoft Entra ID account configured in Duo.
  2. Click the Duo application tile.
  1. The browser redirects to the Duo authentication page. Enter the correct credentials and complete Duo MFA verification.

If the configuration is correct, the browser redirects to GDMS or GWN Manager, and the user is automatically logged in with the appropriate role.

SAML SSO LOGS

Administrators can review authentication activity for SAML SSO users using system logs, which can be reviewed in the following systems:

  • GDMS
  • GWN Manager
  • Microsoft Entra ID
  • AD FS
  • Duo

Reviewing logs from both the Service Provider and Identity Provider can help identify configuration or authentication issues.

Viewing Logs in GDMS

GDMS records SAML login and logout events in the System Log.

  1. Log in to GDMS using an administrator account.
  2. Access the Account Center logs using one of the following paths, depending on the module in use:
    • UC Module: Navigate to System→System Log→Account Center.
    • Networking Module: Navigate to Organization→Change Log→Account Center.
GDMS SAML SSO Logs

Viewing Logs in GWN Manager

GWN Manager also records SAML authentication events in its system log.

  1. Log in to GWN Manager using an administrator account.
  2. Navigate to Organization→Change Log→Account Center.
GWN Manager SAML SSO Logs

Viewing Logs in Microsoft Entra ID

Microsoft Entra ID records SAML authentication activity in the Sign-in Logs.

  1. Log in to the Microsoft Entra Admin Center.
  2. Under Enterprise Applications, select the service provider app.
  3. Navigate to Identity→Monitoring→Sign-in logs.
Microsoft Entra ID SAML SSO Logs

Viewing Logs in AD FS

When AD FS is used as the Identity Provider, SAML authentication events are recorded in the Windows Event Viewer.

  1. Log in to the AD FS server, open Event Viewer by running eventvwr.msc or searching for “Event Viewer” in the Start menu.
  2. In the left pane, navigate to Applications and Services Logs→AD FS→Admin.
  3. Review the events listed.

You can use the Find function to reach for “SAML” events.

AD FS SAML SSO Logs

Viewing Logs in Duo

Duo records authentication activity in the Authentication Log, which includes SAML authentication events.

  1. Log in to the Duo Admin Panel.
  2. Navigate to Reports→Authentication Log.
  3. Use the search filters to locate events related to the configured SAML application.
DUO SAML SSO Logs

Was this article helpful?

Related Articles

Need Support?
Can’t find the answer you’re looking for? Don’t worry we’re here to help!
Contact Support