Adobe Sign inkluderer SAML-godkendelse for kunder, der ønsker et samlet loginsystem.

Introduktion

Standarden Security Assertion Markup Language (SAML) 2.0 muliggør sikker udveksling af brugergodkendelsesdata mellem webprogrammer og identitetstjenesteudbydere.

Når du bruger SAML 2.0-protokollen for at aktivere Enkeltlogon (SSO), sender sikkerhedstokens, der indeholder Assertioner, oplysninger om en slutbruger (hovedbruger), mellem en SAML-autoritet – en identitetsudbyder
(IdP)
, og en SAML-forbruger – en tjenesteudbyder (SP)

Adobe Sign, der fungerer som tjenesteudbyderen (SP), understøtter enkeltlogon via SAML ved at bruge eksterne identitetsudbydere (IdP'er) såsom Okta, OneLogin, Oracle Federated Identity (OIF) og Microsoft Active Directory Federation Service. Adobe Sign er kompatibel med alle eksterne IdP'er, der understøtter SAML 2.0.

Få flere oplysninger om integration med disse identitetsudbydere (IdP'er) i følgende vejledninger:

Du kan også konfigurere Adobe Sign til enkeltlogon (SSO) med andre systemer, der allerede bruges i din organisation, f.eks. Salesforce.com eller andre udbydere, der understøtter SAML 2.0.

Adobe Sign anvender samlet godkendelse i modsætning til delegeret godkendelse. Samlet godkendelse validerer ikke brugerens faktiske adgangskode i Adobe Sign. I stedet modtager Adobe Sign en SAML-bedømmelse i en HTTP POST-anmodning. Adobe Sign understøtter også krypterede bedømmelser.

SAML-assertion har en begrænset gyldighedsperiode, indeholder et entydigt id og er digitalt underskrevet. Hvis assertion stadig er i sin gyldighedsperiode, har et id, der ikke har været brugt før, og har en gyldig signatur fra en pålidelig identitetsudbyder, gives brugeren adgang til Adobe Sign.

Der er en oversigt over Adobe Sign-godkendelsesspecifikationen i tabellen nedenfor:

Specifikation (standardnavn) Værdi
Samlingsprotokol SAML 2.0
Samlingsprofil Browsermeddelelse
Entydigt id for samling Mailadresse
Relætilstand Kræves ikke.  Adobe Sign har logikken til at vise, hvor brugere skal peges hen, efter de er godkendt.  
4-1(a1)

Krav

For at kunne aktivere SSO skal dit firmanetværk understøtte SAML 2.0-protokollen. Hvis dit firmanetværk ikke understøtter SAML, skal du kontakte Adobe Sign Support for at diskutere andre muligheder for at aktivere enkeltlogon på din konto.

Før du begynder at konfigurere SAML SSO, skal du gøre følgende:

  • Gør krav på og etabler dit domænenavn. (for eksemplerne i denne vejledning vil det være rrassoc.com)
  • Aktivere SAML for dit domæne ved hjælp af en udbyder som Microsoft Active Directory Federation, Okta, Onelogin, Oracle Identity Federation eller andre. Du skal muligvis åbne en Adobe Sign-supportanmodning for at få dit domæne aktiveret fra backend.
  • Oprette eller bekræfte, at du har en administratorkonto, med din IdP vha. en mailadresse (for eksemplerne i denne vejledning vil denne mailadresse være susan@rrassoc.com.)
  • (Valgfrit) Tilføj et ekstra mail-id for Bruergklargøring i både IdP og SP. Dette giver dig mulighed for at tilføje flere brugere, der kan logge på Adobe Sign med deres SSO-legitimationsoplysninger.
  • (Obligatorisk) Bekræft, at du har en administratorbruger for Adobe Sign og en administratorbruger for IdP'en.
    (Valgfrit) Opret eller bekræft, at du har en Adobe Sign-administratorkonto, der anvender samme mailadresse som kontoen til din IdP (for eksemplerne i denne vejledning vil denne mailadresse være susan@rrassoc.com) Dette gør det nemmere for dig at administrere kontiene.
  • I Adobe Sign skal du indstille din SAML-tilstand til "SAML tilladt". (Se Arbejde med SAML-indstillingerne for at få flere oplysninger.)

Bemærk:

Når du konfigurerer SAML SSO, anbefaler vi, at du indstiller SAML-tilstanden til SAML tilladt, indtil hele konfigurationsprocessen er færdig, og du har bekræftet, at den virker korrekt. Når dette er bekræftet, kan du ændre SAML-tilstanden til SAML Obligatorisk.

Aktivering af enkeltlogon ved hjælp af SAML

På et højt niveau involverer aktivering af SAML SSO mellem Adobe Sign (SP) og din IdP følgende trin på højt niveau:

1. Konfigurer din IdP (hvis din IdP kræver det) ved hjælp af Oplysninger om Adobe Sign-tjenesteudbyder (SP).

2. Konfigurer Adobe Sign ved hjælp af oplysninger fra din IdP.

3. Bekræft, at SAML sso er konfigureret korrekt. 

Arbejde med SAML-indstillinger

For at finde dine Adobe Sign SAML-indstillinger skal du logge på som kontoadministrator eller gruppeadministrator og derefter klikke på Konto. Under Kontoindstillinger skal du klikke på SAML-indstillinger

2. SAML UI - Unbranded

For at se indstillingerne for Brugeroprettelse, Tilpasning af loginside, Konfiguration af identitetsudbyder (IdP) og Oplysninger om Adobe Sign-tjenesteudbyder (SP) skal du rulle ned til bunden af siden med SAML-indstillinger. 

Indstillinger for SAML-tilstand

I Adobe Sign er der tre indstillinger for SAML-tilstanden og en ekstra indstilling, der virker med SAML Obligatorisk.

7-1(a3)
  • SAML Deaktiveret – aktivér denne indstilling, hvis du ikke bruger SAML til din konto. Når indstillingen er aktiveret, er én af SAML-indstillingerne tilgængelige.
  • SAML Tilladt – aktivér denne indstillingen for at tillade alle brugere, inkl. kontoadministratorer, at bruge SAML SSO. Brugere kan også fortsætte med at brugere deres Adobe Sign-legitimationsoplysninger.
  • SAML Obligatorisk – aktivér denne indstilling for at håndhæve login med SAML SSO for alle brugere. 

Som anført ovenfor under Krav anbefaler vi, at du indstiller SAML-tilstand til SAML Tilladt, indtil du har bekræftet din konfiguration af SAML SSO.

Værtsnavn

Værtsnavnet er dit domænenavn. (Se Krav ovenfor.) Når det angives, bliver
en del af assertion-URL-adressen for forbrugeren, URL-adressen for enkeltlogout (SLO) og URL-adressen for enkeltlogin. 

7-2(a4)

Indstillinger for brugeroprettelse

Kun den første af de to indstillinger for brugeroprettelse er direkte forbundet til SAML-konfiguration. Den anden indstilling vedrører alle ventende brugere, uanset om de er tilføjet som et resultat af godkendelse via SAML eller ej.

8-1(a5)
  • Tilføj automatisk brugere, der er godkendt via – hvis denne indstilling er aktiveret, tilføjes brugere, der godkendes via din IdP, automatisk som ventende brugere i Adobe Sign.
  • Gør automatisk ventende brugere på min konto aktiv – hvis indstillingen "Kræv, at underskrivere på min konto logger på Adobe Sign før underskrivelse" under Bekræftelse af underskrivers identitet (sikkerhedsindstillinger) er aktiveret, bør denne indstilling også være aktiveret. Når der anmodes om en signatur fra en ny bruger, oprettes denne bruger som en ventende bruger på din konto. Hvis denne indstilling ikke er aktiveret, forhindres disse brugere i at underskrive aftaler, der sendes til dem til underskrivelse. 

Indstillinger for tilpasning af loginsiden

Du kan tilpasse loginmeddelelsen, som brugere ser på Adobe Signs loginside, når SAML-enkeltlogin er aktiveret. 

8-2(a6)
  • Loginmeddelelse for enkeltlogon – du kan valgfrit skrive en meddelelse, der vises over loginknappen til SSO på Adobe Signs loginside. Nedenfor er der eksempler på en brugerdefineret loginmeddelelse for SSO og standardmeddelelsen for SSO, i dette tilfælde for Okta, og standardmeddelelsen.
7-1 Authentication - Rebranded
7-2 Authentication - Rebranded

Konfiguration af identitetsudbyder (IdP) i Adobe Sign

For at konfigurere de fleste IdP'er, med undtagelse af Okta, skal du angive oplysninger fra din IdP i IdP-konfigurationsfelterne i Adobe Sign.

10-1(a9)
  • Enheds-id/udbyder-URL – denne værdi leveres af IdP'en for at identificere dit domæne entydigt.
  • Logout URL/SLO-slutpunkt – når nogen logger af Adobe Sign, kaldes denne URL-adresse for også at logge dem af IdP'en.
  • Login URL/SSO-slutpunkt – URL-adressen, som Adobe Sign kalder for at anmode om et brugerlogin fra IdP'en.  Den IdP, der er ansvarlig for at godkende og logge brugeren på.
  • IdP-certifikat – det godkendelsescertifikat, der er udstedt af din IdP.

Oplysninger om Adobe Sign SAML-tjenesteudbyder (SP)

Sektionen med SP-oplysninger viser standardoplysningerne for Adobe Sign. Når du har angivet og gemt dit værtsnavn og oplysninger om IdP-konfiguration, opdateres oplysningerne i sektionen med SP-oplysninger til at inkludere dit værtsnavn.

(I vores eksempel bliver https://secure.echosign.com/public/samlConsume
til https://globalcorp.na1.echosign.com/public/samlConsume.)

11-1(a10)

De angivne SP-oplysninger er, som følger:

  • Enheds-id/SAML-publikum – en URL-adresse, som beskriver den enhed, der forventes at modtage SAML-beskeden. I dette tilfælde er det URL-adressen til Adobe Sign.
  • SP-certifikat – visse udbydere kræver, at der bruges et certifikat til at identificere tjenesteudbyderen. Linket i denne visning peger på certifikatet til Adobe Sign-tjenesteudbyder.
  • Assertion-URL-adresse for forbruger – dette er tilbagekaldelsen, som IdP'en vil sende for at bede Adobe Sign om at logge en bruger på.
  • URL-adresse for enkeltlogout (SLO) – den URL-adresse, som brugere omdirigeres til, når de logger af.
  • URL-adresse for enkeltlogon – dette er den URL-adresse, som IdP'en vil sende loginanmodninger til.

Download

Microsoft Active Directory Federation Services Configuration

Overview

This document describes the process for setting up Single Sign On for Adobe Sign using Microsoft Active Directory Federation Service. Before proceeding, please review the Adobe Sign Single Sign On Using SAML Guide, which describes the SAML set up process and provides detailed information on the SAML Settings in Adobe Sign.

  • The process of setting up SAML SSO includes the following:
  • Installing the Active Directory Domain Service
  • Installing the Active Directory Federation Service
  • Creating a Test User 
  • Adding Adobe Sign as a relying party

Installing the Active Directory Domain Service

Before configuring SAML for MSAD, you must install the Active Directory Domain Service if it is not already installed. You must have system administrator privileges in Windows Server to install Active Directory Domain Services. 

Installing the Active Directory Federation Service

1. If required, launch the Server Manager, then click Dashboard.

3-1(a11)

2. In the Dashboard, click Add roles and features. The Add Roles and Features Wizard displays.

3. In the Select installation type dialog, select Rule-based or Feature-based Installation then click
Next.

4-1 (a12)

4. In the Select destination server dialog of the wizard, leave the Select a server from the server pool option enabled, select a Server Pool, then click Next.

4-2(a13)

5. In the Select server roles dialog, select Active Directory Federation Services, then click Next.

5-1(a14)

6. In the Confirm installation selections dialog of the wizard, accept all the defaults by clicking Install.

7. On the post install options, select Create the first federation server in a federation server farm.

8. On the Welcome page, leave the options as is and click Next.

6-1 (a15)

9. In the Connect to Active Directory Domain Services dialog of the wizard, select the Administrator account if not by default, then click Next.

7-1 (a16)

10. In the Specify Service Properties dialog, import the pfx file that you created using the steps defined in the Certificate Creation section, enter a Federation Service Display Name, then click Next.

8-1 (a17)

11. In the Specify Service Account dialog, select Use an existing domain user account or group Managed Service Account. Use Administrator as the service account and provide your administrator password, then click Next.

9-1 (a18)

12. In the Specify Configuration Database dialog, select Create a database on this server using Windows Internal Database, then click Next.

10-1 (a19)

13. In the Review Options dialog, click Next.

10-2(a20)

14. In the Prerequisite Checks dialog, once the prerequisite check is done, click Configure.

11-1 (a21)

15. In the Results dialog, ignore the warning and click Close.

11-2(a22)

Adding Adobe Sign as a relying party

1. From the Apps menu, launch AD Federation Service Management.

12-1(a23)

2. In the AD FS console, select Authentication Policies then Edit.

12-2(a24)

3. In the Edit Global Authentication Policy dialog, under both Extranet and Intranet, enable Forms Authentication

13-1(a25)

4. In the AD FS console, under Trust Relationships, select Relying Party Trusts and click Add Relying Party Trust. The Add Relying Party Trust wizard displays.

5. In the Select Data Source dialog of the wizard, enable the Enter Data about the relying party manually option, then click Next.

14-1(a26)

6. In the Specify Display Name dialog, enter a Display Name, then click Next.

14-2(a27)

7. In the Choose Profile dialog, enable the AD FS profile option, then click Next.

15-1(a28)

8. In the Configure Certification dialog there is no certificate to configure, so click Next.

15-2(a29)

9. In the Configure URL dialog, select Enable support for the SAML 2.0 WebSSO protocol and enter the Assertion Consumer URL from Adobe Sign, then click Next.

(See the Hostname section of the Single Sign On with SAML Guide for more information about the Assertion Consume URL.)

16-1(a30)

10. In the Configure Identifiers dialog, enter http://echosign.com for Relying party trust Identifier and click Add, then click Next.

17-1(a31)

11. In the next screen, leave the defaults as-is, and click Next.

17-2(a32)

12. In the Choose Issuance Authorization Rules dialog, confirm that the Permit all users to access the relying party option is enabled.

18-1(a33)

13. In the Ready to Add Trust dialog, click Next.

18-2(a34)

14. In the Finish dialog, click Close.

19-1(a35)

15. In the Edit Claim Rules dialog, click Add Rule.

19-2(a36)

The Add Transform Claim Rule Wizard displays.

 

16.  In the Select Rule Template dialog of the wizard, select Send LDAP Attributes as Claims from the Claim rule template drop-down.

20-1(a37)

17. In the Configure Rule dialog, select the options shown in the dialog and click Finish. Adobe Sign only supports the email address as the unique identifier. You need to select E-Mail Addresses as the LDAP Attribute and E-Mail Address as the Outgoing Claim.

21-1(a38)

18. When the Select Rule Template dialog of the wizard redisplays, select Send Claims Using a Custom Rule from the Claim rule template drop-down, then click Next.

21-2(a39)

19. In the Configure Rule dialog, enter the following:

  • Name of rule—Enter EmailToNameId
  • Custom rule description—enter the following:

c:[Type == "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress"]

=> issue(Type =
"http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier",
Issuer = c.Issuer, OriginalIssuer = c.OriginalIssuer, Value = c.Value,
ValueType = c.ValueType, Properties["http://schemas.xmlsoap.org/ws/2005/05/identity/claimproperties/format"]
= "urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress",
Properties["http://schemas.xmlsoap.org/ws/2005/05/identity/claimproperties/spnamequalifier"]
= "");

22-1(a40)

20. Click Finish. The Add Transform Claim Rule Wizard closes.

21. Back in the Edit Claim Rules for Adobe Sign dialog, click the Issuance Authorization Rules tab and Delegation Authorization rules tab and ensure that the Permit Access to All Users is enabled for both as shown below.

If not, add a rule, so that Permit Access To All Users is enabled.

23-1(a41)
24-1(a42)

22. Click OK to accept all changes can close the Edit Claims Rules for Adobe Sign dialog.

Adding the Certificate from Adobe Sign

1. In the AD FS console, under Trust Relationships, select the Adobe Sign Relying Party click Properties.

2. Once launched, select Authentication Policies and then Edit.

25-1(a43)

3. Select the Signature tab.

4. Click Add and add the SP certificate file you downloaded from Adobe Sign.
(See the Adobe Sign SAML Service Provider (SP) Information section of the SingleSign Onwith SAML Guide for more information about the SP certificate.)

5. Select the Advanced tab and change the Secure Hash Algorithm to SHA-2.

6. Select the Endpoints tab and add the Single Logout (SLO) URL from Adobe Sign.
(See the Hostname section of the SingleSign Onwith SAML Guide for more information about the Single Logout (SLO) URL).

7.  Disable Claims Encryption – Open power shell on the ADFS server and type

8. Set-ADFSRelyingPartyTrust -TargetName "Adobe Sign" -EncryptClaims $false 

 

Adobe Sign specific settings

  • The account should have SAML_AVAILABLE=true
  • Host Name
  • SAML Mode
  • ACCOUNT_USER_ADD_EMAIL_DOMAINS setting to be for example dev.com
  • Select the token signing certificate in ADFS and export it as a cer file ( do not export private key) and add it to the account admins SAML Settings page in Adobe Sign.
26-1(a44)
26-2(a45)

Open this certificate file in notepad, and Adobe Sign Admin copy its contents into the IdP Certificate field in SAML Settings.

Now you should be able to test. 

Certificate Creation

1. On Windows, install openssl. On Mac , openssl is present.

2. Launch a command prompt and type:
openssl req -x509 -newkey rsa:2048 -keyout .pem -out .pem -days <#ofdays>

Enter the following:

  • Country code- US
  • State - Californiacity – San Jose
  • Enter some Organization and Organization unit
  • Common Name- This is the fully qualified name that is the same as your host system name example sjtest.es.com

3. Now create the pkcs12 key
pkcs12 -export -in <yourkeynameCer>.pem -inkey <yourkeyName>.pem -out my_pkcs12.pfx

4. Enter password when prompted

5. Click Import and select the my_pkcs12.pfx selected above and enter password that you provided at pkcs12 export time when prompted

Download

Okta Configuration

Overview

Adobe Sign can support Security Assertion Markup Language (SAML) single sign-on (SSO) using external identity providers (IdPs) such as Okta. This document describes the steps for configuring Adobe Sign for SAML SSO with Okta. This document also provides information on testing your SAML SSO configuration. Before proceeding, please see the Adobe Sign Single Sign On Using SAML Guide, which describes the SAML set up process and provides detailed information on the SAML Settings in Adobe Sign.

Configuring SAML SSO with Okta

You must be an administrator for both your Adobe Sign and Okta accounts to enable SAML SSO. The username for both accounts must be the same. The passwords can be different.

When enabling SAML SSO with Okta, information only needs to be entered in Adobe Sign. Okta has developed a custom Adobe Adobe Sign Provisioning app that makes it unnecessary to transfer the SP Information from Adobe Sign to Okta. 

Bemærk:

Note: For the most up-to-date instructions for Okta, see http://developer.okta.com/docs/guides/setting_up_a_saml_application_in_okta.html

1. Log in to Okta and Adobe Sign in different browsers or in different windows within the same browser.

  • In Okta, log in to your account with the same administrator account you use for your Adobe Sign Admin Account.
3-1 (a46)
  • In Adobe Sign, log in to your account using the same admin account credentials that you use for Okta. 
4-1 (a47)

2. Click the blue Admin button.

4-2 (a48)

3. Click the Add Applications shortcut.

4-3(a49)

The Add Application page displays.

5-1 (a50)

4. In Search, type Adobe Sign.

  • Click the Add button to add the Adobe Sign Provisioning application.
5-2(a51)

The Add Adobe Sign Provisioning wizard launches displaying the General Setting tab.

6-1 - Rebranded

5. Log in to Adobe Sign to obtain your Hostname and Adobe Sign server environment:

  • Log in an an Adobe Sign Account Admin
  • Navigate to: Account > Account Settings > SAML Settings
    • Scroll to the bottom of the page and find the Assertion Consumer URL
    • Copy the string between https://  and  .echosign.com/
      • The first value is your Hostname
      • After the Hostname is the Adobe Sign environment your account resides on (na1, na2, eu1, jp1, etc.)
      • In the below example you would copy rrassoc.na1 (include the dot between values)
okta_-_hostname_andinstance

6. In Okta under General Settings, enter the Hostname.Instance for your Adobe Sign account in the Your Adobe Sign Sub domain field.

 

Click Next to continue. 

Bemærk:

Note: If you don’t want users to automatically log in to Adobe Sign when they log in to Okta, disable the Automatically log in when user lands on the login page option. 

okta_8-1_-_rebranded

7. On the Sign-On Options tab, enable SAML 2.0.

9-1 - Rebranded

The SAML 2.0 section displays.

 

8. Under SAML 2.0, click View Setup Instructions.

10-1 - Rebranded

The Okta How to Configure SAML 2.0 for Adobe Sign page displays in a new browser window. This page includes instructions and the IdP information that you must enter in the Adobe Sign SAML Settings page.

11-1 (a57)

9. Copy the Entity ID/Issuer URL from the Okta page, and enter it into the Entity ID/Issuer URL field in Adobe Sign.
(see the idP Configuration section of the How to Configure SAML 2.0 for Adobe Sign)

Bemærk:

Note: The "Entity ID/Issuer URL" does not need to be a well formatted URL. It can be an any unique value.

12-1 (a58)

10. Copy the Login URL/SSO Endpoint from the Okta page, and enter it into the Login URL/SSO Endpoint field in Adobe Sign.
(see the idP Configuration section of the How to Configure SAML 2.0 for Adobe Sign)

Bemærk:

Note that in Adobe Sign, the Logout URL/SLO Endpoint is before the Login URL/SSO Endpoint.

12-2 (a59)

11. Copy the Logout URL/SLO Endpoint from the Okta page and enter it into the Logout URL/SLO Endpoint field in Adobe Sign.
(see the idP Configuration section of the How to Configure SAML 2.0 for Adobe Sign)

13-1 (a60)

Bemærk:

Note: The Logout URL/SLO Endpoint shown above is only a suggestion. You can actually specify any valid URL (e.g., Google).

12. Copy the IdP Certificate from the Okta page to the IdP Certificate field in Adobe Sign.

  • Make sure there are no spaces or returns after “-----END CERTIFICATE-----“.

(see the idP Configuration section of the How to Configure SAML 2.0 for Adobe Sign)

13-2(a61)

You can close the browser window that displays the Okta How to Configure SAML 2.0 for Adobe Sign page after you copy the IdP Certificate.

 

13. In Adobe Sign, click Save.

14-1 (a62)

14. Click the browser window that displays the Okta Sign-On Options if needed.

15. In the Credential Details section of Sign-On Options (see step 8 above), select Email from the Application username format drop-down, then click Next to continue.

14-2 (a63)

16. Under Provisioning, you have the option to select the Enable provisioning features option. (See Setting up Auto-Provisioning for more information.) Click Next to continue without setting up Auto-provisioning. 

14-3 - Rebranded

Bemærk:

Note: If you enable the Enable provisioning features option, you must enable the Automatically add users authenticated through SAML in SAML settings in Adobe Sign.

17. Under the Assign to People tab, in the People section check the box next to your name to assign at least one active user (yourself), then click Next.

15-1 - Rebranded

18. Click Done.

15-2 - Rebranded

You can now log out of Okta and proceed with testing your SAML setup. (See Testing Your Okta SAML SSO Configuration for more information.)

 

Setting Up Auto-provisioning in Okta

If this option is enabled, and the “Automatically add users authenticated through SAML” option in Adobe Sign is also enabled, you can automatically provision users in Adobe Sign.

16-1 - Rebranded

Setting up Auto-launch for Adobe Sign

You can automatically launch Adobe Sign when you log in to Okta. If this feature is enabled, Adobe Sign will open in a separate window when you log in to Okta. You must have pop-ups enabled in your browser for this feature to work.       

Bemærk:

Note If you also enabled the “Automatically log in when user lands on login page” option, when you launch Okta two Adobe Sign windows will open. 

1. Log in to Okta. Your Home page will display.

2. On the Adobe Sign Provisioning app, cursor over the gear icon, then click to activate it.

Okta 17-2 - Rebranded

3. When the Adobe Sign Provisioning Settings popup displays, click the General tab.

Okta18-1 - Rebranded

4. Enable the Launch this app when I sign into Okta option.

Okta18-2 - Rebranded

5. Click Save.

 

Testing Your Okta SAML SSO Configuration

There are two ways to test your Okta SAML setup. 

Log in to Adobe Sign through Okta

1. If logged in, log out of Okta.

2. Log in to Okta. Your Okta Home page displays.

3. On the Home page, click the Adobe Sign Provisioning app.

Okta 19-1 - Rebranded

You are automatically logged into Adobe Sign.

Okta19-2 - Rebranded

Log in to Adobe Sign using your URL

1.  Enter your company login URL in your browser. The Adobe Sign Sign In page displays.

2. On the Sign In page, click the second Sign In button. If you’ve entered a custom Single Sign On Login Message that message displays above this button. If you have not entered a custom message, the default message displays.

Okta 20-1-3 - Rebranded

You are logged into Adobe Sign.

Okta 20-2 - Rebranded

Download

OneLogin Configuration

Overview

Adobe Sign can support Security Assertion Markup Language (SAML) single sign-on (SSO) using external identity providers (IdPs) such as OneLogin. This document describes the steps for configuring Adobe Sign for SAML SSO with OneLogin. This document also provides information on testing your SAML SSO configuration. Before proceeding, please see the Adobe Sign Single Sign On Using SAML Guide, which describes the SAML set up process and provides detailed information on the SAML Settings in Adobe Sign.

 

Configuring SAML SSO with OneLogin

1. Log in to OneLogin and Adobe Sign in different browsers or in different windows within the same browser.

  • In OneLogin, log in to your account with the same administrator credentials you use for your Adobe Sign Admin Account. 
3-1 (a76)
  • In Adobe Sign, log in to your account using the same admin account credentials you use for OneLogin. The passwords for these two logins do not have to be the same, but you must log in as the administrator for each account.
3-2(a77)

2. In OneLogin, click Add Apps.

4-1 (a78)

3. Search for Adobe Sign.

OneLogin 4-2 - Rebranded

4. Click the row for Adobe Sign.

OneLogin 4-3 - Rebranded

5. In the Add page, under Connectors select SAML 2.0 – user provisioning, then click Save at the top.

OneLogin 5-1- Rebranded

6. Navigate to the SAML Settings page. Note the Hostname for Adobe Sign.

OneLogin 6-1 - unbranded

7. In OneLogin, click the Configuration tab. In the Subdomain field, enter your Hostname from Adobe Sign, then click Save.

6-2(a83)

8. Click the SSO tab.

7-1 (a84)

9. In the SSO tab, click View Details to display the Standard Strength Certificate (2048-bit) page.

7-2 (a85)

10. In the Standard Strength Certificate page that displays, click the Copy to Clipboard button for the X.509 Certificate field to copy the certificate to the clipboard.

8-1 (a86)

If the certificate successfully copies, the rollover text says “Copy to Clipboard” text updates to “Copied”.

 

11. In Adobe Sign, paste the copied certificate into the IdP Certificate field. Be sure to remove any returns that may have been copied. The cursor should be at the end of the last line as shown below. 

8-2 (a87)

12.  In OneLogin, click the Copy to Clipboard button for the Issuer URL.

9-1 (a88)

13. In Adobe Sign, paste the Issuer URL into the Entity ID/Issuer URL field.

9-2 (a89)

14. In OneLogin, click the Copy to Clipboard button for the SAML 2.0 Endpoint (HTTP) URL.

10-1 (a90)

15. In Adobe Sign, right click to paste the SAML 2.0 Endpoint (HTTP) URL in the IdP Login URL field. 

10-2 (a91)

16. In OneLogin, click the Copy to Clipboard button next to SLO Endpoint (HTTP).

11-1 (a92)

Bemærk:

Note: The OneLogin SAML 2.0 Endpoint URL is only a suggestion. You can actually specify any valid URL (e.g., Google).

17. In Adobe Sign, copy the SLO Endpoint value into the Logout URL/SLO Endpoint field.

11-2 (a93)

18. In Adobe Sign, click Save.

11-3(a94)

19. In OneLogin, click the back arrow to return to the SSO page.

12-1 (a95)

20. Click the Users tab to add users.

12-2 (a96)

21. Click the row to add the user. The Save button is not activated until you click at least one user.

12-3(a97)

22. When done, click Save

 

Testing Your OneLogin SAML SSO Configuration

There are two ways to test your OneLogin SAML Setup. 

Log in to Adobe Sign through OneLogin

1. If logged in, log out of Adobe Sign.

2. Log in to OneLogin.

13-1 (a98)

3. On the App Home page, click the Adobe Sign app.

OneLogin 13-2 - Rebranded

You are automatically logged into Adobe Sign.

OneLogin 13-3 - rebranded

Log in to Adobe Sign using your URL

1. Enter your company login URL for Adobe Sign in the address line of your browser (such as myCompany.adobesign.com). The Adobe Sign Sign In page
displays.

2. On the Sign In page, click the second Sign In button. If you’ve entered a custom Single Sign On Login Message that message displays above this button. If you have not entered a custom message, the default message displays.

OneLogin 14-1 - Rebranded

3. You are logged into Adobe Sign.

OneLogin 14-3 - rebranded

Download

Oracle Identity Federation Configuration

Overview

Adobe Sign can support Security Assertion Markup Language (SAML) single sign-on (SSO) using external identity providers (IdPs) such as Oracle Identity Federation (11g). This document describes the steps for configuring Adobe Sign, acting as the SAML consumer or service provider (SP), to use OIF. This document also provides suggested steps for configuring OIF, however, please contact your OIF system administrator before making any configuration changes to your OIF Server. Before proceeding, please see the Adobe Sign Single Sign On Using SAML Guide, which describes the SAML set up process and provides detailed information on the SAML Settings in Adobe Sign.

Configuring OIF as an IdP in Adobe Sign

Your organization’s instance of OIF needs to be configured within Adobe Sign as the external SAML Identity Provider (IdP). As an administrator for your Adobe Sign Account, navigate to SAML Setting in Adobe Sign as an (Account | Account Settings | SAML Settings).

You will need metadata information from your OIF IdP
configuration. Typically, the metadata for the OIF is available as an XML
content at: http://:/fed/idp/metadata.
Please contact your OIF administrator to gather the relevant. You will need the
following configuration information.

  • Entity ID/Issuer URL—The entityID attribute on EntityDescriptor element
  • Logout URL/SLO Endpoint—When someone logs out of Adobe Sign, this URL is called to log them out of the IdP as well.
  • Login URL/SSO Endpoint—The Location attribute on SingleSignOnService element
  • IdP Certificate—Certificate information under the element EntityDescriptor -> IDPSSODescriptor -> KeyDescriptor use="signing"

 

This information should be configured in the appropriate fields in the Adobe Sign SAML configuration. See image below:

OIF 4-1 - Unbranded

Configuring Adobe Sign as a SP in OIF

Once the OIF SAML configuration is complete within the Adobe Sign UI, the next step is to configure Adobe Sign as a Service Provider within OIF. The information required for configuring Adobe Sign within OIF is available on the Adobe Sign SAML Service Provider (SP) information section under Account | Account Settings | SAML Settings

OIF 5-1 - unbranded

The metadata description for Adobe Sign is shown below:

code(a105)

Download

You must customize this metadata description and change the highlighted section in the XML to match the URL for your account. The Assertion Consumer URL for your specific account is shown in SAML Settings.

 

The steps for completing the configuration in OIF are as follows:

1. Go to the Federations configuration screen on the OIF Administration panel

7-1 (a106)

2. Create a new federation profile

7-2 (a107)

3. Create a new Service Provider (SP) listing for Adobe Sign

 

Import the Adobe Sign SP configuration XML or manually create the SP listing using the provider information from the Adobe Sign SAML settings.

8-1 (a108)

4. Complete the configuration. Adobe Sign will appear as a new Service Provider listing in the OIF list of SPs. 

8-2 (a109)

Verifying Email Address as NameID Format

Adobe Sign uses email address as the unique user identifier. Before testing the single sign-on one last step is the ensure that the email address field is mapped to the appropriate user attribute within OIF and that email address is enabled as a valid NameID format.

9-1 (a110)
9-2 (a111)

Download

©2016 Adobe Systems Incorporated. All Rights Reserved.

Products mentioned in this document, such as the services of identity providers Microsoft Active Directory Federation, Okta, Onelogin, and Oracle Identity Federation, and Salesforce software retain all of the copyrights and trademark rights of their specific corporations.

 

Sidst opdateret: 23. juni 2016

Dette arbejde har licens under en Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Opslag på Twitter™ og Facebook er ikke omfattet af vilkårene for Creative Commons.

Juridiske meddelelser   |   Politik for beskyttelse af personlige oplysninger online