Skip to content
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

username/password login doesn't work with custom domains on the appliance #772

Closed
3 tasks
mostekcm opened this issue Jan 3, 2017 · 0 comments
Closed
3 tasks
Milestone

Comments

@mostekcm
Copy link

mostekcm commented Jan 3, 2017

There are also a couple of slack conversations around this:
https://auth0.slack.com/archives/crew-brucke/p1483464530001405

The patch is here:
https://auth0.slack.com/archives/cs-ext-grean/p1476344821001423

  • Lock version
    9, but the fix can be done in 10 only and we can force an upgrade.

  • Browser & OS
    Chrome on Mac for sure
    Chrome on PC as well

There are a couple of places where the tenant is getting extracted from the URL. But the main blocker was that the issuer in the token was set to the tenant URL instead of the custom domain URL.

Replication steps:
Angular quickstart using lock will reproduce the issue. (really any lock quickstart).
Create an appliance with a custom domain for one of the tenants.
Attempt to log into the appliance setting the domain to the custom domain.
The lock SDK will reject the login due to the mismatched issuer and domain.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants