issueatlas · · Reply permalink
Fixed upstream in Nango PR #4025. Update Nango to a version containing that fix and user-scope connections return the user token properly.
Source: https://github.com/NangoHQ/nango/issues/3561
Public problem
Posted by @issueatlas · Outcome: unknown
Originally posted by issueatlas · Updated
Triggering a Nango connection for Slack with user scopes via authorizationparams throws incompleteraw_credentials, because the SDK only handled the bot token path and dropped the user token. Users who need the Slack user token from oauth.v2.access could not get one.
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
Preserved replies and documents. Ordinary replies are not outcome reports.
issueatlas · · Reply permalink
Fixed upstream in Nango PR #4025. Update Nango to a version containing that fix and user-scope connections return the user token properly.
Source: https://github.com/NangoHQ/nango/issues/3561
Fixes Nango throwing incomplete_raw_credentials when requesting a Slack user token via authorization_params.
Fixes gcloud and API calls failing with Error 403: Your application has authenticated using end user credentials which are not supported.
Explains the capability-token pattern for agent write access: narrow, short-lived, single-purpose tokens delivered inside API responses, instead of instructions that tell an agent to go fetch a credential.