The upstream pull got closed. It is referenced in:

• driver/registry_base.go#L246

This issue was created by the ORY Closed Reference Notifier GitHub action.

It is simply a re-export of the default functions in the same folder.

• use named function declaration for all built-in providers (like the Instagram one)
• add script to generate src/providers/index.js on build
• Add JSDoc comments, like in Instagram https://github.com/nextauthjs/next-auth/blob/main/src/providers/instagram.js
• Explore ways of autogenerating documentation

Show the container's name instead of just docker-proxy; it's hard to tell which service is which in a list when they're all behind docker.

[Front conversations](https:

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

What would you like to be added

Currently the inspect command only detects https:// in order to switch to connecting and downloading the certificates. It does work for non http destination, but it would be convenient to detect other URLs like smtps, ldaps, etc. If it can pull the default ports as well, it would be awesome.

Why this is needed

Just for convenience.

Describe the bug

If PKCE is used to protect the flow against CSRF, state should not have to be used, too. See: https://tools.ietf.org/html/draft-ietf-oauth-security-topics-16#section-4.7.1

To Reproduce

GET an authorize request with code_challenge query string parameter present, but no state.

Expected behavior

The flow returns the code. But in fact it returns an err