-
## Issue
**Server Setup Information**:
docker using wekanteam/wekan:v4.93
wekan behind a nginx proxy.
reachable as https://wekan.domain.tl/wekan
ldap configured => works
normal user => works
oa…
-
Hello!
I have a problem with the gatekeeper in my app.
We have settings of accsess token in keyclock, where his lifetime is 10 minutes and lifetime of refresh token is 6 hours.
But after 10 m…
-
## Context
The original behavior of Wildly was having an redirect from / to /auth. After the migration you just get a "Resource not found".
## Alternatives
Keep without.
-
Hello,
please comment on this issue...
Case reproduces on Firefox browser, on Chrome works OK.
###### Scenario:
User logs in then logs out.
The user changes clock on machine back in time - from…
ghost updated
4 years ago
-
###### Environment
- lua-resty-openidc version: 1.7.5
- OpenID Connect provider: Red Hat Single Sign On (Based on Keycloak)
###### Expected behaviour
When refreshing tokens, the OIDC library…
-
### Preflight Checklist
- [X] I agree to follow the [Code of Conduct](https://github.com/dexidp/dex/blob/master/.github/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the …
-
### Current Behavior
The openid-connect plugin will randomly redirect requests with valid session cookie and non-expired tokens back through the authentication flow. No errors were generated as the r…
-
We do have this quote often and today - right as I was typing this report - it finally occurred to me. We use Google Cloud Platform + custom SSO server. And we think that the problem lies that there a…
-
The provider logout does not work for oidc providers that requires the id_token_hint parameter. This is a recommanded parameter in the OIDC specifications (https://openid.net/specs/openid-connect-rpin…
-
Good day!
I ran my test installation through this guide (https://docs.nginx.com/nginx/deployment-guides/single-sign-on/keycloak/)
And started to get infinite loop after access token expired.
It s…