-
I suggest implementing the [OIDC dynamic client registration protocol](https://openid.net/specs/openid-connect-registration-1_0.html).
I understand that it seems in contradiction with the `one sing…
-
## What I did?
Installed loginpass using pipenv. Used the example to pull in Google and Azure provider. Tried to log in using Azure provider.
The authorization is below, it is incredibly simple. …
-
Given that the most widely used authentication protocol is OAuth, this seems like a good candidate to try to fit into WebAccessControl, along with [WebID-TLS](https://www.w3.org/2005/Incubator/webid/s…
-
### Description:
When a Custom Oauth provisioned new user logs in using an invite link, the login flow breaks at early stage.
It is not fatal as you can proceed with refresh of the browser windo…
-
All installed ok, but unable to connect to my Keycloak identity provider. Config:
```
Rails.application.config.middleware.use OmniAuth::Builder do
provider :open_id, :store => OpenID::Store::Fi…
-
dokieli is currently (v0.3.20) using https://github.com/solid/solid-auth-client/ to handle WebID-OIDC based authentication. User clicks 'Sign in' from the dokieli menu, and then presented with "OpenID…
-
In addition to #28 and #87
muety updated
3 weeks ago
-
### Summary
We can setup Keycloak as an Identity Provider (IdP) for both authentication and authorization while maintaining the existing user management system as the primary user system. For this …
-
Hi Nikos!
As commented before I attach some things that I have found that may need some clarification or modification:
1. How is authentication done in Authorization Code Flow? Is it done via id…
-
## Describe the question
When setting `--username` in kubeconfig, there is no Browser opening keycloak for asking username and password, just asking in terminale directly. Thats very nice. When the u…