[jira] [Commented] (QPID-7346) [Java Broker] Improve Principals to record their origin

["Keith Wall (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/QPID-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15374719#comment-15374719 ] 

Keith Wall commented on QPID-7346:
----------------------------------

Principals to keep a reference back to the AuthenticationProvider that created it.   There serial form is to include the reference to the AuthenticationProvider.

Preference store needs to record the serialised form of the Principal (include authentication type, name).
For preference we will have a generic authenticated principal and generic group principal.  These objects will be created as the preference owner and visibilityList are recovered from the store.  The generic principals keep the original name and type.

> [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
>
>
> 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 jira should include making the UserPreferences layer take advantage of this when (de-)serialising principals (i.e., {{owner}} and {{visibilityList}})  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org