-
-
Notifications
You must be signed in to change notification settings - Fork 388
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
Help - Configure sign in with Apple #1813
Comments
I'll check it. As a first step, could you please see if error in |
Logs for v.1.13.0: 2024/09/19 22:04:21.899 [DEBUG] {provider/apple.go:244 provider.(*AppleHandler).LoginHandler} login with apple
2024/09/19 22:04:21.899 [ERROR] {provider/apple.go:281 provider.(*AppleHandler).LoginHandler} prepare login url for [apple] provider failed
2024/09/19 22:04:21.899 [INFO] {rest/httperrors.go:39 rest.SendErrorJSON} prepare login url for [apple] provider failed - response_mode must be form_post if scope is not empty - 500 - 88.112.34.153 - /auth/apple/login?from=https://comment.harrytang.xyz/web/iframe.html?selfClose&site=harrytang.xyz [caused by auth/provider/apple.go:282 provider.(*AppleHandler).LoginHandler]
2024/09/19 22:04:21.899 [ERROR] {provider/apple.go:281 provider.(*AppleHandler).LoginHandler} prepare login url for [apple] provider failed
2024/09/19 22:04:21.899 [INFO] {logger/logger.go:134 logger.(*Middleware).Handler-fm.(*Middleware).Handler.func1.1} GET - /auth/apple/login?from=https://comment.harrytang.xyz/web/iframe.html?selfClose&site=harrytang.xyz - comment.harrytang.xyz - 586fcf4504d9 - 500 (58) - 193.402µs - ad74f07f-c1e6-9587-8013-350ba02efd33
2024/09/19 22:05:08.215 [DEBUG] {middleware/auth.go:75 middleware.(*Authenticator).Auth.(*Authenticator).auth.func1} auth failed, invalid kind of token v.1.12.0: 2024/09/19 22:25:41.909 [DEBUG] {provider/apple.go:244 provider.(*AppleHandler).LoginHandler} login with apple
2024/09/19 22:25:41.909 [ERROR] {provider/apple.go:281 provider.(*AppleHandler).LoginHandler} prepare login url for [apple] provider failed
2024/09/19 22:25:41.909 [INFO] {rest/httperrors.go:39 rest.SendErrorJSON} prepare login url for [apple] provider failed - response_mode must be form_post if scope is not empty - 500 - 88.112.34.153 - /auth/apple/login?from=https://comment.harrytang.xyz/web/iframe.html?selfClose&site=harrytang.xyz [caused by auth/provider/apple.go:282 provider.(*AppleHandler).LoginHandler]
2024/09/19 22:25:41.910 [INFO] {logger/logger.go:134 logger.(*Middleware).Handler.func1.1} GET - /auth/apple/login?from=https://comment.harrytang.xyz/web/iframe.html?selfClose&site=harrytang.xyz - comment.harrytang.xyz - 586fcf4504d9 - 500 (58) - 1.051848ms - c07d0617-3dfa-992d-98be-b5c90a7c0933
2024/09/19 22:25:41.909 [ERROR] {provider/apple.go:281 provider.(*AppleHandler).LoginHandler} prepare login url for [apple] provider failed |
The UI problem is due to cached wrong version of CSS, force-reload of the page (or incognito mode) would fix that. There seem to be some breaking CSS change between master and one of the versions you tested. I'll check what to do with |
According to what I see in the code, the current |
Thank you, now it deployed. |
Current master behaviour in Safari: after login, iframe.html is downloaded from Chrome: after login, Afterwards, I am not logged in on the comments page right away, but shown as logged in after page refresh. I'll think how to handle this. It's improvement over not working login, but doesn't sound like working fine. |
Hi, I see that Apple Login in the live demo works just fine, is it running the |
Yes, it is working on demo. I need to do something about iframe.html behaviour when it receives POST request: I guess there is some custom setup on demo to make it work. |
Hi,
I got the error:
prepare login url for [apple] provider failed
I did follow the doc very carefully but could not make it work.
I have my remark42 (v1.13.1) running at
https://comment.harrytang.xyz/
. This is my Web Authentication Configuration in Apple:I don't know if something not correct, any help really appreciated! Thanks
Here is the logs:
The text was updated successfully, but these errors were encountered: