Versions Compared

Old Version 12

changes.mady.by.user Unknown User (bimminger)

Saved on

compared with

New Version 13

changes.mady.by.user Unknown User (scheipner)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The signer will see an additional external authentication option. A pop-up appears, where the signer has to enter his credentials to authenticate. eSignAnyWhere will receive a temporary token to receive some authentication information, which will be stored in the audit log of the envelope. You can integrate any external OAuth 2.0 service. For example the open source project OAuthServer (https://oauthserver.codeplex.com/) would enable you to connect your AD/LDAP via OAuth 2.0 and eSignAnyWhere, or you can implement your own OAuth 2.0 service.

Info

The following two OAuth2 configuration examples show you chapters show, based on examples, how to configure itOAuth2 authentication. Because some of these examples are based on external services, the procedure may change by time. They should show you the basic concept tow to configure OAuth2. Note: To force a specific user and configure validation rules, the OAuth2 provider must return a JWT token or offer a resource uri that provides user data in JSON format (e.g. an OIDC /userinfo endpoint)!

...

  1. In the Azure portal, in App registrations, select your application.

  2. Under Manage, select Authentication.

  3. Under Platform configurations, select Add a platform.

  4. Under Configure platforms, select the tile "Web" to configure a web app.

  5. Enter the following Redirect URI (either one or both):
    1. for User Authentication in eSignAnywhere: https://<eSignAnyWhere URL>/Account/ValidateOAuth (e.g.: https://demo.esignanywhere.net/Account/ValidateOAuth)
    2. for Signer Authentication in eSignAnyWhere: https://<eSignAnyWhere URL>/SawViewer/HttpHandlers/AuthHandler.ashx (e.g.: https://demo.esignanywhere.net/SawViewer/HttpHandlers/AuthHandler.ashx)

  6. Select Configure to complete the platform configuration.

  7. Under Implicit grant and hybrid flows (still on the Authentication page) make sure "ID tokens (used for implicit and hyprid flows)" is enabled
  8. Leave Allow public client flows disabled, this is not needed.
  9. Click Save to complete the configuration

...