• Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None
    • False
    • None
    • False

      Usage:

      Here's a demo that shows how it should work. The assigned user then needs to go into external logins and accept the authorization. We did this because showing the token to the org admin exposes a possible permission escalation.
      The assigned user will still need to a member of the org with the correct team permissions, as oauth tokens only work for authn and not authz 

      https://redhat-internal.slack.com/archives/G7VFPAY7Q/p1719926842517859?thread_ts=1719911793.845159&cid=G7VFPAY7Q

       

      New Test case:

      OCP-74391 - Org owner can change ownership of API tokens

              szhao@redhat.com Sean Zhao
              rhn-support-dyan Dongbo Yan
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: