![]() The JWT flow is recommended for Service Integrations if you're writing the app for your own organization's use. TL DR - watch my screencast where I focus on this exact issue. I'm sorry that the documentation for Service Integrations is not clear. I have no problem with this but why advise against using it then advise against using the alternative as well? Am I missing something? So should I not use these grants? If I don't it leaves me back at using Legacy Header authentication. This grant is not suitable for service integrations. However, both the Authorization Code Grant and the Implicit Grant pages state at the very top of the page User consent can start with either the Authorization Code Grant or the Implicit Grant. Then in the granting consent section it states So I decided to go to that Service Integration Authentication page which statesīefore an application can impersonate a user, the application must get consent directly from the user or from their account administrator. DocuSign recommends new service integrations be built with Service Integration Authentication. Legacy Header authentication was formerly recommended for service integrations. This advises against using it for service integrations ![]() I began by looking into authentication info and found the Legacy Header page. I am creating a service integration that will need to use my Docusign account.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |