Got a query regarding my favorite OpenShift identity provider:
htpasswd Identity Provider.
Why "must" the htpasswd secret be created in the openshift-config
This isn't something I just absolutely have to know. However,
more times than not, I like to look underhood at things. If it
truly is a "must" that the secret be created in the openshift-config
namespace,then so be it. Still, I'd like to take the opportunity to
add something extra to my knowledgebase.
I did a tiny bit of digging, but nothing that could/would qualify as
an exhaustive search
@Trevor An old query - but seems I have to try put my thoughts here.
Oauth Server responsible for authenication expects to check the secret in the openshift-config namespace ( OpenShift reads all the internal configuration-related information from this namespace resources. ).
If you create it elsewhere, OpenShift wont be able to find it for authentication. it provides the necessary isolation and ease of management for all the authentication related secrets.
The query is old, but your fresh information ensures that
the query will not go stale!!! Your second paragraph makes
a very impactful point!!!
As always, many thanks for expanding my knowledgebase