The Wayback Machine - https://web.archive.org/web/20210906053644/https://github.com/topics/oauth
Skip to content
#

oauth

Here are 1,854 public repositories matching this topic...

next-auth
svkoskin
svkoskin commented Aug 27, 2021

Description 🐜

When using Credentials provider, the authorize callback should receive the incoming message object as the second parameter. However, on certain Node versions the incoming message has undefined as headers.

This happens on Node versions 14.15.2, >=15.1 and >=16.0 and is related to this change: nodejs/node#35281 There is an issue on Node but it is clo

sailorfrag
sailorfrag commented Jul 14, 2021

On Windows, if the authentication flow isn't completed (failure, closed the browser, etc.) then the client keeps showing 'connecting' but doesn't show a clear action to restart authentication.

Clicking disconnect + connect, or log in as a different user will generate a new authentication link and unblock the user, but that's somewhat difficult to discover.

Options for improvement include adding

mccutchen
mccutchen commented May 1, 2019

Is your feature request related to a problem? Please describe.

The public key-based request signing functionality added to sso_proxy in buzzfeed/sso#106 is undocumented. In particular, it's not immediately obvious how to a) generate an appropriate keypair or b) validate a signed request in an upstream service.

Describe the solution you'd like

New documenta

cli

Improve this page

Add a description, image, and links to the oauth topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the oauth topic, visit your repo's landing page and select "manage topics."

Learn more