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

connector: fix path that connectors listen on #522

Merged
merged 1 commit into from Jul 25, 2016

Conversation

ericchiang
Copy link
Contributor

When Dex uses a non-root issuer URL, it current assumes that all
path prefixes will be trimmed by an upstream proxy (e.g. nginx).
This means that all paths rendered in HTML will be absolute to the
prefix, but the handlers still listen at the root.

Connectors are currently the only component that registers at a
non-root URL. Make this conform with the rest of Dex by having the
server determine the path the connector listens as rather than the
connector itself.

Updates #502

Note that this is part of a larger conversation about what it means
for Dex to be at a non-root URL path. See #521.

@xaka can you test this to ensure it works with your setup?

@sym3tri
Copy link

sym3tri commented Jul 25, 2016

LGTM

@ericchiang
Copy link
Contributor Author

One sec. The fix doesn't quite work.

When Dex uses a non-root issuer URL, it current assumes that all
path prefixes will be trimmed by an upstream proxy (e.g. nginx).
This means that all paths rendered in HTML will be absolute to the
prefix, but the handlers still listen at the root.

Connectors are currently the only component that registers at a
non-root URL. Make this conform with the rest of Dex by having the
server determine the path the connector listens as rather than the
connector itself.
@ericchiang ericchiang merged commit 1e0ee1e into dexidp:master Jul 25, 2016
@ericchiang ericchiang deleted the fix-connector-handlers branch November 22, 2016 20:07
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

Successfully merging this pull request may close these issues.

None yet

2 participants