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

Update cf dex connector to use the `authorization_endpoint` #2649

Open
pivotal-jwinters opened this Issue Oct 3, 2018 · 1 comment

Comments

Projects
None yet
3 participants
@pivotal-jwinters
Copy link
Contributor

pivotal-jwinters commented Oct 3, 2018

Issue to track:
concourse/dex#4

@pivotal-jwinters pivotal-jwinters changed the title Update cf dex connector to use the `authorization_endpoint` from the cloud foundry /v2/info endpoint Update cf dex connector to use the `authorization_endpoint` Oct 3, 2018

@gobeila

This comment has been minimized.

Copy link

gobeila commented Dec 17, 2018

Has a version been targeted for the correction of this?

This issue prevents us from updating our Concourse instances to 4 since we use CF authentication on an external SSO provider (SAML). The token_endpoint points to the internal UAA of CF while the authorization_endpoint points to the authentication provider.

This seems to be already fixed in dex: concourse/dex@0d46e2e

@vito vito added the triage label Jan 9, 2019

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