You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (JIRA)" <ji...@apache.org> on 2016/03/30 09:41:25 UTC

[jira] [Commented] (QPID-7093) Make the display of createdBy/lastUpdatedBy user information human readable

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

Keith Wall commented on QPID-7093:
----------------------------------

There is a decision to be made about how the clients of the model get the displayable userid for a given object.

* The model could be extended to have {{displayableCreatedBy}}/{{displayedLastUpdatedBy}} derived attributes.  After recovery, once the services of the authentication providers are available, these attributes would somehow need to be populated as part of an extra recovery step.  This seems awkward.
* The client of the model could make separate calls to the authentication provider to resolve userid to there displayable counterparts.  There could be an Authentication Provider operation to do this.   This seems ugly.   It would mean that an an Operator of virtualhost X, I would need permission on the Broker level object.
*  We make displayableCreatedBy/displayedLastUpdatedBy persisted values and have them be set on creation/update by taking the displayable name from the authenticated prinicipal.  We would accept the fact that the displayable name could go stale.

> Make the display of createdBy/lastUpdatedBy user information human readable
> ---------------------------------------------------------------------------
>
>                 Key: QPID-7093
>                 URL: https://issues.apache.org/jira/browse/QPID-7093
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker
>            Reporter: Keith Wall
>             Fix For: qpid-java-6.1
>
>
> For some authentication providers, the id that represents a person is not human readable.  For instance, when using the Google OAuth2, the identities are 16 digit numbers.  This present a usability problem in the web management console when viewing audit trail information createdBy/lastUpdateBy as the operator will have no reasonable way to find out the name of the user that created or updated an object.
> Authentication Providers will have the ability to resolve a userid into a displayable name (QPID-7168).



--
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