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

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

I've read the docs, and it seems you can pass through knex instances, but I didn't see if it supports SQLite3 - could you clarify please?

One of the major topics in an enterprise application is encryption at rest. With SQL server 2016+ it is possible to do encryption at rest. .Net Core wasn't compatible until recently, which I think now supports only TDE (Transparent Data Encryption).

I don't know enough to implement enough, but here's an article I found.

https://docs.microsoft.com/en-us/aspnet/core/security/data-protection/c

The following guides may be improved with unit test examples:

• https://github.com/danschultzer/pow/blob/master/guides/custom_controllers.md
• https://github.com/danschultzer/pow/blob/master/guides/sync_user.md
• https://github.com/danschultzer/pow/blob/master/guides/lock_users.md
• https://github.com/danschultzer/pow/blob/master/guides/user_roles.md

There's alread

See the-road-to-graphql/fullstack-apollo-express-postgresql-boilerplate#5 for users domain. Maybe someone wants to add tests for the messages domain too.