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
I am using a self-hosted instance of Logto as an OIDC provider for my GetOutline application. My domain is configured with Cloudflare. When attempting to sign in via Logto, I successfully authenticate using my email and password. However, the GetOutline application fails to proceed with authentication and reports an error.
Upon checking the logs, I noticed that the response Outline received from Logto contained a Cloudflare challenge (HTML page), instead of the expected JSON response. This issue causes authentication to fail completely.
Expected behavior
Logto should:
Detect the Cloudflare challenge and handle it internally before responding to the OIDC client (Outline).
Ensure the application receives a valid JSON response for proper OIDC authentication.
How to reproduce?
Configure a self-hosted Logto instance with a domain parked on Cloudflare.
Configure a self-hosted GetOutline instance to use Logto as its OIDC provider.
Attempt to log in to Outline using Logto for authentication.
Authentication fails, and logs show that Outline received a Cloudflare challenge from Logto instead of the expected JSON.
Context
Logto Cloud
Self-hosted, Logto version = v1.23.0
Container (Docker image)
Raw Node.js
Screenshots
The text was updated successfully, but these errors were encountered:
Describe the bug
I am using a self-hosted instance of Logto as an OIDC provider for my GetOutline application. My domain is configured with Cloudflare. When attempting to sign in via Logto, I successfully authenticate using my email and password. However, the GetOutline application fails to proceed with authentication and reports an error.
Upon checking the logs, I noticed that the response Outline received from Logto contained a Cloudflare challenge (HTML page), instead of the expected JSON response. This issue causes authentication to fail completely.
Expected behavior
Logto should:
How to reproduce?
Context
Screenshots
The text was updated successfully, but these errors were encountered: