ddea31193b
OpenID connect has become a standard when it comes to authentication and in order to fix a security concern around forwarding authentication and authorization information it has been decided to add support for it. This feature is in beta version and only enabled when there is a configuration for it. Before enabling it in production, please consider that it's in beta with potential bugs and that there are several production critical features still missing such as all OIDC related data is stored in configuration or memory. This means you are potentially going to experience issues with HA deployments, or when restarting a single instance specifically related to OIDC. We are still working on adding the remaining set of features before making it GA as soon as possible. Related to #189 Co-authored-by: Clement Michaud <clement.michaud34@gmail.com> |
||
|---|---|---|
| .. | ||
| access_control.go | ||
| authentication.go | ||
| configuration.go | ||
| const.go | ||
| duo.go | ||
| identity_providers.go | ||
| notifier.go | ||
| regulation.go | ||
| server.go | ||
| session.go | ||
| shared.go | ||
| storage.go | ||
| totp.go | ||
| validator.go | ||
| validator_test.go | ||