Add OIDC authentication or error message about support authentication methods

[briedel]

I was trying to use the python client against a kubernetes cluster that uses OIDC authentication. The python-client tried to log in as an "anonymous" user, which failed. It would be good to add OIDC authentication or add an error message that the authentication method was not support.

[mbohlool]

[mbohlool]

kubernetes-client/python-base#31 is implementing this.

[briedel]

Thanks for the hint! I used the code from kubernetes-client/python-base#31 and found that there is a difference between how kubectl behaves and the python API. When a refresh token is necessary, kubectl does not require idp-certificate-authority-data to be set:

    if cfg[cfgCertificateAuthorityData] != "" {
        certAuthData, err = base64.StdEncoding.DecodeString(cfg[cfgCertificateAuthorityData])
        if err != nil {
            return nil, err
        }
    }

The error that is called seems to be suppressed somehow. Yet, with the same config the new oidc authentication requires idp-certificate-authority-data to be set:

ConfigException: Invalid kube-config file. Expected key idp-certificate-authority-data in kube-config/users[...]/user/auth-provider/config

There is a refresh-token URL provided in the config though, which might be what allows kubectl to get around the need for idp-certificate-authority-data

[lichen2013]

This issue is the same as #195

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[benley]

It appears this may be addressed via kubernetes-client/python-base#48; should this issue be closed?

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.