-
-
Notifications
You must be signed in to change notification settings - Fork 122
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sso with apple id not working #406
Comments
I've fixed this issue, but unfortunately couldn't confirm it since I need to wait for my Service ID provisioning - could you give this build a try? https://github.com/warp-tech/warpgate/actions/runs/3352578787 |
I have now an other error message, but I think the url in the apple config is right - I used https://server-url/@warpgate/api/sso/return |
This means that the redirect URL generated by Warpgate doesn't match the one set in the Sign in with Apple configuration - you can see the actual redirect URL inside the SSO URL that Warpgate sends you to, e.g.:
<-- |
ah I see the problem. that's the url:
and there ist the port 8888 hard coded? how can I change this? as my server is listen on port 443. in the config I have:
also if i append the port, there will still be 8888 used. |
I see - you have a reverse proxy in front, right? Currently Warpgate is not aware that frontend and backend port numbers can differ and will use the port number from the config file to construct the URL. I'll need to add a new |
yes right, I have a proxy in front. |
Should be fixed now - see https://github.com/warp-tech/warpgate/wiki/Warpgate-behind-a-reverse-proxy for configuration |
Finally fixed! Please note that the config layout is now changed too - Warpgate will now generate the JWT token for you |
i have setup sso with apple id, but when try to login i get the message "
invalid_request - response_mode must be form_post when ...
" (see screenshot for full message)i found something about this in the apple forum, not sure if this also related to my issue.
any idea how i can fix this?
The text was updated successfully, but these errors were encountered: