You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I set up MAS (matrix-authentication-service) with keycloak backend.
When i login with element X i can login.
Next step, verify Session:
I get the notification on another client (Element, Schildichat, both on Android and Linux desktop)
But element X stuck forever in "Waiting for another Device"
When i try to login with element oder Element-web, the verification-process works fluently with MAS and keycloak-backend also on the same device.
To Reproduce
Steps to reproduce the behavior:
Login with OIDC on Element X (MAS is configured for synapse)
Verify Device/Session
Accept verification-request on another device (Element/Schildichat...)
Wait forever on Element X to get the next screen.
Expected behavior
Verification on Element X working.
Screenshots
Desktop (please complete the following information):
Smartphone (please complete the following information):
Describe the bug
I set up MAS (matrix-authentication-service) with keycloak backend.
When i login with element X i can login.
Next step, verify Session:
I get the notification on another client (Element, Schildichat, both on Android and Linux desktop)
But element X stuck forever in "Waiting for another Device"
When i try to login with element oder Element-web, the verification-process works fluently with MAS and keycloak-backend also on the same device.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Verification on Element X working.
Screenshots
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Matrix-synapse 1.114.0 with integrated sliding-sync
matrix-authentication-service: v0.12.0
Identity-Provider: keycloak
When element x tries to start the verification-process for the new session i get this in homeserver.log
The text was updated successfully, but these errors were encountered: