Uploaded image for project: 'Hybrid Cloud Console'
  1. Hybrid Cloud Console
  2. RHCLOUD-35541

So access checks can be consistent between users and service accounts, use service account user ID for group membership relations and delete them when we detect the service account is removed

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • Unset
    • CRCPLAN-232 - AuthZ | PRBAC v2 Service Provider Migration Initiation (Internal)
    • None

      When Principals are lazily created, ensure they use the user_id value from SSO, and use this value for group membership tuples (this may happen already as part of RHCLOUD-35448)

      Deletion is moved to another story RHCLOUD-35628

              rhit-ahenning Alec Henninger
              rhit-ahenning Alec Henninger
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: