[ 
https://issues.apache.org/jira/browse/QPID-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lorenz Quack updated QPID-7346:
-------------------------------
    Description: 
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}})  

  was:
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, ...).


> [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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to