Description
At the moment it seems not possible to use Kuberpult with Dex when Dex shall be addressed via an Ingress URL. For the creation of the Dex URL that is opened by Kuberpult when hitting the login button for Dex in the Kuberpult UI, the Helm Chart parameter 'auth.dexAuth.fullNameOverride' is used, which does only make sense when Kuberpult shall communicate with Dex within the Kubernetes Cluster.
Steps for recreation
I want to use Kuberpult together with Dex.
Both services run in the same Kubernetes Cluster in the same namespace. I installed and configured Dex via the Kuberpult Helm Chart.
I configured 'baseURL' for Dex with the Ingress URL of Dex and 'useClusterInternalCommunicationToDex' with false. Dex is enabled.
When I hit the login button for Dex in the Kuberpult UI, I get the error message:
'Get "http://kuberpult-dex:5556/dex/.well-known/openid-configuration": dial tcp :5556: connect: connection refused'
When I now overwrite the default value of 'auth.dexAuth.fullNameOverride' (which contains 'kuberpult-dex' by default) with an empty string, I get the following error message:
'Get "http://:5556/dex/.well-known/openid-configuration": dial tcp :5556: connect: connection refused'
This tells me that 'fullNameOverride' is used to assemble the Dex URL.
However, this doesn't make sense in this context, since I deactivated the cluster internal communication and provided the Ingress URL of Dex as baseURL.
Expected behavior
The Dex URL is being assembled from the parameter 'baseURL', and https is being used when useClusterInternalCommunicationToDex is set to false and when the baseURL starts with https.
Description
At the moment it seems not possible to use Kuberpult with Dex when Dex shall be addressed via an Ingress URL. For the creation of the Dex URL that is opened by Kuberpult when hitting the login button for Dex in the Kuberpult UI, the Helm Chart parameter 'auth.dexAuth.fullNameOverride' is used, which does only make sense when Kuberpult shall communicate with Dex within the Kubernetes Cluster.
Steps for recreation
I want to use Kuberpult together with Dex.
Both services run in the same Kubernetes Cluster in the same namespace. I installed and configured Dex via the Kuberpult Helm Chart.
I configured 'baseURL' for Dex with the Ingress URL of Dex and 'useClusterInternalCommunicationToDex' with false. Dex is enabled.
When I hit the login button for Dex in the Kuberpult UI, I get the error message:
'Get "http://kuberpult-dex:5556/dex/.well-known/openid-configuration": dial tcp :5556: connect: connection refused'
When I now overwrite the default value of 'auth.dexAuth.fullNameOverride' (which contains 'kuberpult-dex' by default) with an empty string, I get the following error message:
'Get "http://:5556/dex/.well-known/openid-configuration": dial tcp :5556: connect: connection refused'
This tells me that 'fullNameOverride' is used to assemble the Dex URL.
However, this doesn't make sense in this context, since I deactivated the cluster internal communication and provided the Ingress URL of Dex as baseURL.
Expected behavior
The Dex URL is being assembled from the parameter 'baseURL', and https is being used when useClusterInternalCommunicationToDex is set to false and when the baseURL starts with https.