-
This package has only oidc and saml client support, but requested to have docker-v2 protocol client support.
knvpk updated
3 years ago
-
### Description
On OIDC User Info (experimental) feature, Symfony Security Bundle configuration allows to pass a custom client, or auto-create a client with the configuration passed (e.g.: `base_ur…
-
There are many scenarios in which the user is logged in to the IdP but the IdP does not want to issue a token in the assertion endpoint response, such as wanting to re-authenticate the user, or needin…
-
Hello, please write some documentation, the description is scant, what should I do about it? do I understand correctly that the application should follow http://app.app.example/logout where nginx loc…
-
## Summary
We recently updated our test concourse system from `7.4.0` to `7.8.0` and noticed our OIDC has stopped working. We use a self-signed certificate for testing and this has worked without iss…
-
## Problem
The documentation for this attribute is inadequate. Here's the definition:
```
plugins = lib.mkOption {
type = with lib.types; functionTo (listOf package);
default = _: …
-
Hey.
I'm reading the OIDC specs and other articles and looking for information on how to implement a proper support for sessions.
The protocol states the use of `session_state` but I havent find o…
-
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Is your feature request related to a problem? Please describe the problem.
https://twitter.com/davidfowl…
-
Please consider switching the list usage from:
```
oidcProviders:
- ingressHostname: example.com
...
- ingressHostname: example2.com
...
```
to dict usage like this:
```
…
-
**Describe** **描述**
- config.toml
```
[Oidc]
Enable = true
ClientId = "yearning"
ClientSecret = "xxx"
Scope = "email openid profile"
AuthUrl = "https://keycloak.extension.sopei/realms/sopei-de…