home

Contracts

Adobe Sign ServicesAdvantage Platform AdministrationApprovals for Advantage PlatformApprovals for SalesforceBilling for Advantage PlatformBilling for SalesforceCLM for Advantage PlatformCLM for SalesforceContracts for SalesforceCollaborateComposer for Advantage PlatformComposer for SalesforceContractsConga for Google DocsConga Upgrade ProgramContract Intelligence (Standalone)CPQ for Advantage PlatformCPQ for SalesforceDeal MaximizerDigital Commerce for Advantage PlatformDigital Commerce for SalesforceDiscovery AI for Advantage PlatformDiscovery AI for SalesforceDocusign ServiceseSignature Integration with Advantage PlatformGridInvoice GenerationMix FormsOrchestrateOrder Management for Advantage PlatformOrder Management for SalesforcePartner Commerce for Advantage PlatformPartner Commerce for SalesforceQuote GenerationSign for Advantage PlatformSign for SalesforceSmart SearchTurboEnginesX-Author for Contracts 1.0 (Classic)X-Author for ContractsX-Author for Contracts Advanced for Advantage PlatformX-Author for Contracts Advanced for SalesforceX-Author for ExcelX-Author for Migration ManagerRelease NotesGeneral
Adobe Sign ServicesAdvantage Platform AdministrationApprovals for Advantage PlatformApprovals for SalesforceBilling for Advantage PlatformBilling for SalesforceCLM for Advantage PlatformCLM for SalesforceContracts for SalesforceCollaborateComposer for Advantage PlatformComposer for SalesforceContractsConga for Google DocsConga Upgrade ProgramContract Intelligence (Standalone)CPQ for Advantage PlatformCPQ for SalesforceDeal MaximizerDigital Commerce for Advantage PlatformDigital Commerce for SalesforceDiscovery AI for Advantage PlatformDiscovery AI for SalesforceDocusign ServiceseSignature Integration with Advantage PlatformGridInvoice GenerationMix FormsOrchestrateOrder Management for Advantage PlatformOrder Management for SalesforcePartner Commerce for Advantage PlatformPartner Commerce for SalesforceQuote GenerationSign for Advantage PlatformSign for SalesforceSmart SearchTurboEnginesX-Author for Contracts 1.0 (Classic)X-Author for ContractsX-Author for Contracts Advanced for Advantage PlatformX-Author for Contracts Advanced for SalesforceX-Author for ExcelX-Author for Migration ManagerRelease NotesGeneral

Conga Product Documentation

Welcome to the new doc site. Some of your old bookmarks will no longer work. Please use the search bar to find your desired topic.

Show Contents

Contracts

Conga Contracts Single Sign On (SSO)

download

Example AD FS 2.0 Configuration

This is a quick example of configuring the Relying Party Trust in AD FS 2.0 with SAML 2.0. This guide will not cover setting up and configuring the AD FS system on a Windows Server. For more information on initial setup, please consult the Microsoft setup and configuration guides. To configure the Relying Party Trust in AD FS 2.0 with SAML 2.0, take the following steps:

  1. Go toAdministrative Tools.and click on AD FS 2.0 Management Console.
  2. Click on Trust Relationships section, and then Relying Party Trusts
  3. Add Relying Party Trust.
  4. On the Select Data Source screen, select to Enter data about the relying party manually.
  5. Select a descriptive display name for service. This is only for your organization and does not impact the integration.
  6. Select the AD FS 2.0 Profile. SAML2 was not introduced until version 2.0 of AD FS.
  7. Skip the Configure Certificate step.
  8. Check the Enable Support for the SAML 2.0 WebSSO protocol box and enter the URL provided by Contracts for the Relying party SAML 2.0 SSO service URL.
  9. Enter in the issuer that the Contracts AuthnRequest provides. It is sso.novatuscontracts.com by default but this identifier must be unique across all relying party trusts so if more than one is configured ( as in for testing purposes), a different identifier needs to be entered for each user.
  10. Select issuance authorization rules. This is determined by the organization, but it is easiest to just permit all users access to this relying party. The following screen is a summary screen.
  11. Click next to add the trust relationship.
  12. On the final page, leave the Open the Edit Claim Rules dialog for this relying party trust when the wizard closes unchecked and click the close button to launch the dialog.
  13. The dialog opens to the first tab for Issuance Transform Rules. Click the Add Rule… button at the bottom of the screen.
    This launches the Add Transformation Claim Wizard.
  14. Select the Send LDAP Attributes as Claims as the Claim rule template to user.
  15. For the claim rule name, select any descriptive name. For example, you can use “Default Mapping”.
  16. Click the attribute store dropdown and select Active Directory. Now for the basic authentication only scheme, Contracts will only need to map the first attribute, which is User-‐Principal-‐ Name LDAP attribute to the Name ID outgoing claim type. The rest of the attributes shown are necessary to handle authorization as well.
  17. Click Finish.
  18. Relying Party Trust is configured and ready to be used.
Administrator Guide
Contracts

January 2, 2025