WHAT

Originally from discussion https://groups.google.com/a/redhat.com/g/mk-support/c/jnjO2PzO6rA and then further clarified during discussions in the comments below.

• Users with access to manage ACLs should not be restricted from creating ACLs with themselves as the named principal
• Errors/warnings from the server are not displayed in the UI if they occur when creating a new ACL
• It may be helpful to display the owner's ACLs (read only) in some form to indicate that they do not need to be added by the user/owner
• Improve the error message returned by the authorizer when owners attempt to create ACLs for themselves
• It would be helpful to more seamlessly support assignment of ACLs to the current owner ahead of, or during, an owner change (descoped)

HOW

Changes in the UI, Admin API server and the ACL authorizer in the kas-broker plugins.  See JIRAs under this Epic for details.

DONE

• Issues resolved and supporting tests added, probably at the unit and the within the end to end test suite.