Skip to content

feature request: auth-provider oidc #195

Description

@vasu1124

I just injected an additional case in kube_config.py in function _load_gcp_token()

if self._user['auth-provider']['name'] == 'oidc':
  self.token = "Bearer %s" % self._user['auth-provider']['config']['id-token']
  return self.token

Works for me, but does not cover the refresh of the token and other features of oidc.

Would be nice to also get proper support for oidc (and not only gcp)

Thanks!

Activity

  1. lichen2013 commented on Jan 26, 2018

    @lichen2013

    This issue is the same as #368

  2. added
    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
    on Oct 30, 2018
  3. fejta-bot commented on Apr 26, 2019

    @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

  4. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Apr 26, 2019
  5. fejta-bot commented on May 26, 2019

    @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

  6. added
    lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.
    and removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on May 26, 2019
  7. benley commented on May 26, 2019

    @benley

    /remove-lifecycle rotten

  8. removed
    lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.
    on May 26, 2019
  9. benley commented on May 26, 2019

    @benley

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

  10. fejta-bot commented on Aug 24, 2019

    @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

  11. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Aug 24, 2019
  12. yliaog commented on Sep 3, 2019

    @yliaog
    Contributor

    /close

  13. k8s-ci-robot commented on Sep 3, 2019

    @k8s-ci-robot
    Contributor

    @yliaog: Closing this issue.

    Details

    In response to this:

    /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.

  14. added a commit that references this issue on Jan 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    feature-requesthelp wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.help-neededlifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions