Describe the bug

After Hydra startup log warns about configuration key deprecation. There is no records in documentation reference (https://www.ory.sh/hydra/docs/reference/configuration/) about oidc.subject_identifiers.supported_types.

Reproducing the bug

Steps to reproduce the behavior:

Start Hydra Hydra v1.9.0-alpha.2 with oidc.subject_identifiers.enabled set to public

_Se

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

go-jwt seems to not be maintained really. It has open/known security issue (which have multiple PRs open to address, earliest in 2018: dgrijalva/jwt-go#286). And it requires numbers to be floats because it cannot validate ints. [PR to fix this has been made](https://github.com/dgrijalva

Description

Some frameworks do not support PKCS #1 OR SEC1 EC formats for the private key and require the use of PKCS #8.
See smallstep/autocert#17 (comment)

We should add the flag --pkcs8 or --format pkcs8 to at least the following commands:

• step ca certificate
• step ca sign
• step ca renew

Autocert should also support thi