[
https://issues.apache.org/jira/browse/QPID-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15434880#comment-15434880
]
Lorenz Quack commented on QPID-7346:
------------------------------------
I changed AbstractQueue to fix exclusiveOwner.
I am inclined to leave the other code changes in place. The JIRA was about
giving every Principal knowledge about it's origin. In some cases (currently
the ones outlined above) they choose to not do anything with it but for
consistency I would leave the code in place regardless.
regarding the Anonymous auth provider I don't consider it special enough to
treat it any different from the other auth providers. If someone creates
multiple anon auth providers (I could not imagine why but they might have their
reasons) they quite possibly want to distinguish them.
> [Java Broker] Improve Principals to record their origin
> -------------------------------------------------------
>
> Key: QPID-7346
> URL: https://issues.apache.org/jira/browse/QPID-7346
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Lorenz Quack
> Fix For: qpid-java-6.1
>
> Attachments:
> 0001-QPID-7346-Java-Broker-WIP-Save-the-origin-of-a-Princ.patch,
> reverting-changes-for-principal-databases.diff
>
>
> Currently the broker uses a variety of different Principals (e.g.,
> {{UsernamePrincipal}}, {{GroupPrincipal}}, ...).
> To make (de-)serialisation and future migration to a more sophisticate
> principal representation easier the principals should capture their origin
> (e.g., {{OAuth2AuthenticationProvider}}, {{FileBasedGroupProvider}}, ...).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
