So fosite has ES256 support, I have seen some past PRs to support ES256 in Hydra (ory/hydra#628, ory/hydra#627), but looking at the code I do not see it really being supported in Hydra.

While RS256 is recommended by the spec, ES256 is close to that with its "Recommended+" recommendation. Support

Issues 🎫 :

• Add TypeScript issue template
• Reword current templates
• Require bug reports to have a reproduction
• Check out Beta issue templates

Automation 🤖 :

• introduce CODEOWNERS, add @lluia and @balazsorban44 for TypeScript
• Add N

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

Though https://www.home-assistant.io/ runs on what appears to be Debian, neither deb nor apt are present and all add-on functionality is expected to be done via Home Assistant plugins.

Describe the solution you'd like

It would be great to have Tailscale support as a HassIO plug-in for Home Assistant.

**Describe alte

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