-
Notifications
You must be signed in to change notification settings - Fork 557
Closed
Description
Currently, if I use the OIDC auth mode I must insert a client-secret
attribute to the userConfig
:
this.kc.loadFromClusterAndUser(
{
caData: '<CA-data>',
name: 'k8s-cluster',
server: 'https://127.0.0.1:6443',
skipTLSVerify: false,
},
{
authProvider: {
name: 'oidc',
config: {
'client-id': 'kubernetes-vilmos-test',
'id-token': '<id-token>',
'idp-issuer-url': 'https://<keycloak-server-url>/auth/realms/<realm-id>',
'refresh-token': '<refresh-token>',
'client-secret': ' ', // I MUST include this with some random value even if the keycloak server is set up not to require a `client-secret`.
},
},
name: 'user-k8s',
});
As far as I understand:
- the
cliend-secret
is an optional parameter in the OIDC specifications (if the oidc server doesn't want to authenticate the clients, it can be omitted) - there's a check for it in the
oidc_auth
file
Metadata
Metadata
Assignees
Labels
No labels