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.

Sign up for GitHub

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

Jump to bottom

Harbor OIDC login fails with custom Okta enpoint using Let's Encrypt certificate #120

Closed
crdant opened this issue Nov 25, 2020 · 0 comments · Fixed by #125
Closed

Harbor OIDC login fails with custom Okta enpoint using Let's Encrypt certificate #120

crdant opened this issue Nov 25, 2020 · 0 comments · Fixed by #125

Comments

@crdant
Copy link
Contributor

crdant commented Nov 25, 2020 •
edited
Loading

Just like with #118, when you've got a custom URL and issuer on Okta and use Let's Encrypt for certs on it, Harbor will fail because LE isn't a trusted CA in image it's built from. I originally addressed this in #105, but #100 switched to using the new extension mechanism and invalidated that approach. Waiting on #108 to be complete before submitting a PR on this one.

I'll be using the same approach to this as #119, leveraging the overlay from #112 and the method from #115.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Enables Harbor to trust Let's Encrypt crdant/tkg-lab
1 participant
@crdant