activitypods / activitypods/activitypods
OIDC login: sessions are not registered when logging/registering through Pod frontend
- Dominant language
- JavaScript
- Stars
- 260
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
When logging or signing up directly through the Pod provider frontend, no information are registered through the node-oidc-provider library
- No interactionId are passed through the `auth.registered` or `auth.connected` events
- In Redis, no AccessToken, AuthorizationCode, Grant, Session are saved.
The result is, when we try to connect with an application, we are continously redirected to the login screen (with a `no_session` reason), which itself keep on redirecting to the Authorization screen, as on the frontend, we believe to be connected.
The only way to make it work is to disconnect from the Pod provider frontend, go to the application and login through the application.
Even if we don't use Solid-OIDC to connect directly to the Pod provider frontend, we need to go through the node-oidc-provider library to make this work.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.