Replies: 1 comment 1 reply
-
Hmm, that's indeed a bug due to the multiple tenants setup. The server tries to match the login session with the current tenant, which is desirable in most cases. However, since I'll make a fix ASAP. Thank you for reporting! |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I have a self-hosted version of Fief (0.26.0), with the default Fief workspace and multiple Tenant.
I configured Github OAuth as described, and activated for a specific tenant.
From my Next JS app, i see the following process:
https://myapp.com/login
(provided by fief-js) -> returns HTTP 307https://fief.myapp.com/mytenant/authorize?response_type=code&...
-> returns HTTP 302https://fief.myapp.com/mytenant/login
-> returns HTTP 200https://fief.myapp.com/oauth/authorize?tenant=xxxxxxx&provider=xxxxxxx
-> returns HTTP 302https://github.com/login/oauth/authorize?response_type=code&client_id=xxxx&redirect_uri=https%3A%2F%2Ffief.myapp.com%2Foauth%2Fcallback&state=xxxx&scope=offline_access+openid+user+user%3Aemail
-> returns HTTP 302https://fief.myapp.com/oauth/callback?code=xxxx&state=xxxx
-> returns HTTP 400With the error "Invalid login session"
What did i do wrong ?
Beta Was this translation helpful? Give feedback.
All reactions