Harbor OIDC login fails with custom Okta enpoint using Let's Encrypt certificate
crdant opened this issue · 0 comments
crdant commented
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.