We have an existing Docusign integration that relies on JWT authentication. Part of the setup is creating a ‘master token’ that is used to verify the application (above). The old one expired in test and production and now the integration fails to work in both environments. The issue may be the JWT I am creating has the incorrect header and payload. I have tried the format below: { "typ": "MT", "alg": "RS256", "kid": "5a983aca-6c5c-4ede-811a-9908c5fe281e" } { "iss": "a1000a7e-dc23-4578-9a1f-89fbc07ac03e", "sub": "c845922d-9396-439c-b72f-2daf610315c0", "aud": "account-d.docusign.com", "scope": "signature impersonation" } Any help is appreciated.
↧