Skip to content

Auth0 not working correctly for Azure Entra ID #1750

Closed

Description

@MatthiasRoels

I was experimenting with Parseable on Kubernetes. I managed to set it up (I had some issues with the Helm chart; injecting custom env vars and secrets is currently not possible) with the UI exposed with an ingress resources and OAuth0 enabled via Azure Entra ID. Container image: quay.io/parseablehq/parseable:v2.9.4

The first issue I encountered was an issue with inconsistent documentation (I can create a separate issue for this if needed); Both the OAuth0 and the Azure Entra pages refer to an P_OIDC_REDIRECT_URI env var. However, the configuration page does not mention this and instead mentions a mandatory P_ORIGIN_URI env var. Not: the later seems to be the one for which I got it to work!

The second issue I encounter (and I reused an Entra ID app registration I use for all applications in my cluster so I'm pretty sure it is configured correctly!) is related to the actual authentication process. On the UI, when you click sign in with OAuth0, you are redirected to Azure as expected. However, the url contains a parameter prompt=consent which requires you to request approval every time you try to login. Since it is an app I re-used, I was already added and I still needed approval. When I remove that prompt=consent parameter from the link, it works like a charm, so I guess that param shouldn't be there in the first place? In any case, it works (kinda) but I need to remove that param on every login attempt which is annoying. Anything we can do about this?

Edit: relevant part of the code

Activity

  1. coderabbitai commented on Aug 12, 2026

    @coderabbitai
    Contributor
    🔗 Related PRs

    #1716 - fix: oidc redirect [merged]


    📝 Issue Planner

    Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.

    • Create Plan

    🧪 Issue enrichment is currently in open beta.

    You can configure auto-planning by selecting labels in the issue_enrichment configuration.

    To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

    issue_enrichment:
      auto_enrich:
        enabled: false

    💬 Have feedback or questions? Drop into our discord!

  2. parmesant commented on Aug 12, 2026

    @parmesant
    Contributor

    Hey @MatthiasRoels !
    Thanks for bringing this to our notice. Seems to be an issue with OIDC Scope being set forcibly. Will issue a fix for this ASAP!

  3. self-assigned this
    on Aug 12, 2026
  4. parmesant commented on Aug 14, 2026

    @parmesant
    Contributor

    Hey @MatthiasRoels !
    The PR for this issue is out now #1753
    It will be included in our next release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions