James Elliott ef549f851d feat(oidc): add additional config options, accurate token times, and refactoring (#1991) ... * This gives admins more control over their OIDC installation exposing options that had defaults before. Things like lifespans for authorize codes, access tokens, id tokens, refresh tokens, a option to enable the debug client messages, minimum parameter entropy. It also allows admins to configure the response modes. * Additionally this records specific values about a users session indicating when they performed a specific authz factor so this is represented in the token accurately. * Lastly we also implemented a OIDC key manager which calculates the kid for jwk's using the SHA1 digest instead of being static, or more specifically the first 7 chars. As per https://datatracker.ietf.org/doc/html/draft-ietf-jose-json-web-key#section-8.1.1 the kid should not exceed 8 chars. While it's allowed to exceed 8 chars, it must only be done so with a compelling reason, which we do not have.		2021-07-04 09:44:30 +10:00
..
index.md	feat(configuration): add error and warn log levels (#2050)	2021-06-01 14:09:50 +10:00
oidc.md	feat(oidc): add additional config options, accurate token times, and refactoring (#1991)	2021-07-04 09:44:30 +10:00