Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Surface OAuth errors with request details in Dashboard #471

Closed
rguldener opened this issue Apr 6, 2023 · 1 comment
Closed

Surface OAuth errors with request details in Dashboard #471

rguldener opened this issue Apr 6, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@rguldener
Copy link
Member

Currently when something goes wrong in an OAuth flow (or token refresh) only a generic error is printed on the server logs of Nango server. No errors are visible in the dashboard.

We should surface errors from OAuth flows in the dashboard, along with the details of the API request that was made.
This makes developers who use Nango more independent, because it allows them to see the exact error response from the server.

I can currently think of 3 errors where this is relevant:

OAuth flow errors
We could show these on the integration details page, along with information such as the Connection-ID, timestamp, exact callback URL etc.

Token retrieval errors
We could show these on the integration details page, along with information such as the Connection-ID, timestamp, exact token fetch API request etc.

Token refresh errors
We could show these on the Connection details page, along with information such as the number of previous refreshes, refresh token, timestamp, exact token refresh API request etc.

@rguldener rguldener added the enhancement New feature or request label Apr 6, 2023
@rguldener
Copy link
Member Author

Closing this with the new activity tab. Can re-open if needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant