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
{{ message }}
This repository was archived by the owner on May 25, 2025. It is now read-only.
I had been using keycloak as as my openid provider but am trying to reduce the number of packages to keep up-to-date and because I also have nextcloud running for various other purposes and they have added openid to their bag of tricks, I'm trying to switch over. jitsi-openid is working perfectly with keycloak (thanks for that) but when I try to use it with nextcloud I successfully login and get returned to jitsikeycloak where I receive an error that simply states "Invalid token" there's nothing in the jitsi-openid logs at all and nothing that I can identify as useful info in the logs of the various docker containers running the jitsi-meet installation. Any help/insight would be great appreciated (but of course I understand if my inability to provide meaningful info means that there's nothing you can do).
I had been using keycloak as as my openid provider but am trying to reduce the number of packages to keep up-to-date and because I also have nextcloud running for various other purposes and they have added openid to their bag of tricks, I'm trying to switch over. jitsi-openid is working perfectly with keycloak (thanks for that) but when I try to use it with nextcloud I successfully login and get returned to jitsikeycloak where I receive an error that simply states "Invalid token" there's nothing in the jitsi-openid logs at all and nothing that I can identify as useful info in the logs of the various docker containers running the jitsi-meet installation. Any help/insight would be great appreciated (but of course I understand if my inability to provide meaningful info means that there's nothing you can do).
Thanks,
Seth Green