Docusign embedded sign and code grant authorization

Certified Senior Developer

We are trying to integrate with docusign embedded component in appian. 

I used a code grant authorization with a connected system, with a single user. 

When the token is not valid i go to the connected system and click on authorize.

And like that i can even sign embedded in appian or with the url generated.

The problem is that we have a requirements to provide signing with docusign for two distincted users,

That user are not administrator or designer(like me) so cant click the authorize button everytime.

And i see that in the connected system are not a user reference to pass. 

So how can i authorize two different user with codegrant?

I have to use two different connected system with a different secret keys?

Use an a!authorizationLink?

  Discussion posts and replies are publicly visible

Parents
  • 0
    Certified Lead Developer

    In Appian, you can use OAuth 2.0 Authorization Code Grant to authenticate on behalf of individual users.


    The access token represents the logged-in user, not just the application.

    Appian tracks users through its own platform login, but each user must authorize the integration at least once.

    You configure a Connected System in Appian with OAuth 2.0 using Authorization Code Grant.
    This includes setting the authorization URL, token URL, client ID/secret, and required scopes.

    Appian can store user-scoped tokens (access and refresh tokens) for each individual user.
    When a user calls the integration, Appian checks for a valid token first.
    If none exists, the user is redirected to the OAuth provider to login and consent.

    After authorization, Appian exchanges the code for tokens and stores them for that user.
    This allows integrations to execute API calls in the context of each specific user rather than a shared service account.


    Regards

Reply
  • 0
    Certified Lead Developer

    In Appian, you can use OAuth 2.0 Authorization Code Grant to authenticate on behalf of individual users.


    The access token represents the logged-in user, not just the application.

    Appian tracks users through its own platform login, but each user must authorize the integration at least once.

    You configure a Connected System in Appian with OAuth 2.0 using Authorization Code Grant.
    This includes setting the authorization URL, token URL, client ID/secret, and required scopes.

    Appian can store user-scoped tokens (access and refresh tokens) for each individual user.
    When a user calls the integration, Appian checks for a valid token first.
    If none exists, the user is redirected to the OAuth provider to login and consent.

    After authorization, Appian exchanges the code for tokens and stores them for that user.
    This allows integrations to execute API calls in the context of each specific user rather than a shared service account.


    Regards

Children
No Data