ADFS (SAML) Integration

ADFS (SAML) Integration


This guide for integrating the authentication of ADFS Active Directory users to InfoShield. This document outlines the steps and considerations for a seamless integration process. 

 Note: This integration only initiates authentication and doesn't automatically withdraw users. Therefore, it must be uploaded to users manually beforehand. Subsequently, their login method will be converted to Single Sign-On (SSO) as part of the process.

 

SAML Authentication: Requirements and Steps:

Get IDP (ADFS) metadata XML OR public XML URL`

Note: You can watch this help video for the ADFS team. 
By following these steps, you will successfully integrate the metadata from the IDP ADFS into the LMS system:
  1. Log in to the LMS dashboard as admin.
  2. Navigate to Users section.
  3. Select ADFS/SAML2 from the options.
  4. Paste the metadata into the designated field.

  5. Save Changes

  

SSL keys for InfoShield data 

Place the certificate and key of the web domain in the specified path within the source code: C:\laragon\infoshield-data\saml2
 

 

Export LMS (InfoShield) metadata for the IDP (ADFS) team:

After completing the initial steps, proceed to the LMS InfoShield platform to download the InfoShield metadata.

Dashboard > users > SAML/ADFS then appears in the download file here after putting ADFS metadata.

Helpful video for this step.

 

After completing the outlined steps, the SAML authentication process will be active on the Login page. Users will be able to authenticate using SAML credentials for accessing the system. 

 

 
© 2024 Cerebra All Copyrights Reserved

    • Related Articles

    • Azure Active Directory Integration

      Introduction This document is a guide for integrating the Azure Active Directory users into InfoShield. Azure Integration Requirements Please provide the below requirements. Note: You will need application administrator, application developer, or ...

    • Fetch Azure users without service accounts

      In Azure integration, you can exclude service accounts, meeting rooms, and other accounts using User Creation Restriction by multiple fields, like the below image. We ignore accounts with an empty surname (.+) and then will not bring meeting rooms ...