Skip to content

Dex auth issues conflict between local and external when adding Microsoft Auth #3272

@csanadpoda

Description

@csanadpoda

Validation Checklist

  • I confirm that this is a Kubeflow-related issue.
  • I am reporting this in the appropriate repository.
  • I have followed the Kubeflow installation guidelines.
  • The issue report is detailed and includes version numbers where applicable.
  • I have considered adding my company to the adopters page to support Kubeflow and help the community, since I expect help from the community for my issue (see 1. and 2.).
  • This issue pertains to Kubeflow development.
  • I am available to work on this issue.
  • You can join the CNCF Slack and access our meetings at the Kubeflow Community website. Our channel on the CNCF Slack is here #kubeflow-platform.

Version

master

Detailed Description

Following an installation from manifests to a bare metal cluster (managed by RKE2 if that matters - this is NOT AKS!), I'm trying to add Microsoft Auth to Dex in addition to the default Dex email login. I'm following the guide from the docs, however I get an error about issuer mismatch:

time=2025-11-07T14:13:34.813Z level=ERROR msg="connector returned error when creating callback" connector_id=azure err="expected callback URL "http://dex.auth.svc.cluster.local:5556/dex/callback" did not match the URL in the config "https://kubeflow..sslip.io/dex/callback"" request_id=8340c6af-c1d0-4524-baf1-d8818718f3bf

Obviously I cannot add a local URI as a Redirect URI to the Azure App Registration, so I added https://kubeflow.<my-ip>.sslip.io/dex/callback, but all internals are signed as http://dex.auth.svc.cluster.local:5556/dex. Editing the Dex configmap to contain issuer: https://kubeflow.<my-ip>.sslip.io/dex also doesn't work since that then breaks the regular email login.

How do I set Dex up when deploying Kubeflow from the manifests to enable both regular email login (e.g. [email protected]) but also Azure AD/Microsoft login via Dex?

Steps to Reproduce

  1. Install Kubeflow via manifests
  2. Create an Azure App registration
  3. Add Azure OIDC login as described in the README
  4. Try to log in via Azure

Screenshots or Videos (Optional)

No response

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions