From Bright Pattern Documentation
Jump to: navigation, search
imported>Tracy
 
(Updated via BpDeleteTranslateTags script)
 
Line 1: Line 1:
<translate>= ADFS Console Setup=
+
= 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 17: Line 17:
 
# For mapping, use “UPN” as the ''NameID''.<br /><br />
 
# For mapping, use “UPN” as the ''NameID''.<br /><br />
 
# Add a new mapping: "UPN = CSIMLoginID"
 
# Add a new mapping: "UPN = CSIMLoginID"
 
 
 
 
</translate>
 

Latest revision as of 04:10, 29 May 2024

• 5.19 • 5.2 • 5.3 • 5.8

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

  1. Go to the ADFS Console.

  2. Right-click on Relying Party Trusts and select Add Relying Party Trust.

  3. Select option Enter data about the relying party manually and click Next.

  4. Enter the name for this relying party (e.g., “BPSPTest”).

  5. Select ADFS 2.0 and click Next. Skip the next windows by clicking Next.

  6. Enter the Relying Party URL: https://<bpsp_hostname>/agentdesktop/sso/redirect

  7. On the next screen, select option Permit all users.

  8. Click Next to launch the Claims rules.

  9. In the Claims rules screen, click Add Rule.

  10. Select Send LDAP Attributes as Claims because Agent Desktop will be used as the Claims supplier.

  11. For ClaimRule Name, give a name and enter the Attribute Store.

  12. For mapping, use “UPN” as the NameID.

  13. Add a new mapping: "UPN = CSIMLoginID"
    < Previous | Next >