From Bright Pattern Documentation
Wyler.metge (talk | contribs) (Updated via BpClonePage extension. Source page: draft:Saml2-single-sign-on-integration-guide/ADFSConsoleSetup) |
|||
(One intermediate revision by one other user not shown) | |||
Line 1: | Line 1: | ||
− | + | = ADFS Console Setup= | |
After you have [[saml2-single-sign-on-integration-guide/InstallingADFSonWindowsServer2012|created a test ADFS instance and saved your certificate]], you are ready to set up the ADFS Console. | After you have [[saml2-single-sign-on-integration-guide/InstallingADFSonWindowsServer2012|created a test ADFS instance and saved your certificate]], you are ready to set up the ADFS Console. | ||
Line 19: | Line 19: | ||
− | + | Once the console has been configured, you will be able to [[Saml2-single-sign-on-integration-guide/ConfiguringBrightPatterntoUseSSO|Configure Bright Pattern to Use SSO]] | |
− | |||
− |
Latest revision as of 04:56, 7 March 2025
ADFS Console Setup
After you have created a test ADFS instance and saved your certificate, you are ready to set up the ADFS Console.
Procedure
- Go to the ADFS Console.
- Right-click on Relying Party Trusts and select Add Relying Party Trust.
- Select option Enter data about the relying party manually and click Next.
- Enter the name for this relying party (e.g., “BPSPTest”).
- Select ADFS 2.0 and click Next. Skip the next windows by clicking Next.
- Enter the Relying Party URL: https://<bpsp_hostname>/agentdesktop/sso/redirect
- On the next screen, select option Permit all users.
- Click Next to launch the Claims rules.
- In the Claims rules screen, click Add Rule.
- Select Send LDAP Attributes as Claims because Agent Desktop will be used as the Claims supplier.
- For ClaimRule Name, give a name and enter the Attribute Store.
- For mapping, use “UPN” as the NameID.
- Add a new mapping: "UPN = CSIMLoginID"
Once the console has been configured, you will be able to Configure Bright Pattern to Use SSO