At least in the latest spec: https://openid.net/specs/openid-connect-rpinitiated-1_0.html

Currently Hydra uses id_token_hint to determine if logout is RP-initiated or OP-initiated. I do not think this is possible by relaying on id_token_hint.

Looking at the implementation of issueLogoutVerifier I think the logic is correct (if id_token_hint is missing, you ask for consent, if it is p

Describe the bug

I think this is a similar problem than what was already reported in ory/fosite#434, but elsewhere in the code. I believe all calls to url.QueryUnescape should be removed from the code. Go already escapes all query/form parameters automatically and unescaping again can just break things.

Example:

func GetRedirectURIFromRequestValues(value

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?

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.

@kiwi179 proposes a lookup set for additional functionality

https://wellsb.com/csharp/aspnet/code-first-ef-core-lookup-table-blazor/
https://coding.abel.nu/2013/11/enums-and-lookup-tables-with-ef-code-first/