[
https://issues.apache.org/jira/browse/QPID-7093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7093:
-----------------------------
Description:
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 should have a mechanism to return a human readable
name for any valid user identity. For some authentication providers, this
might be implemented as a query. For others, it might involve maintaining a
cache that is populated as users use the Broker.
was:
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 such have a mechanism to return a human readable name
for any valid user identity. For some authentication providers, this might be
implemented as a query. For others, it might involve maintaining a cache that
is populated as users use the Broker.
> Make the display of createdBy/lastUpdateBy 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
>
> 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 should have a mechanism to return a human readable
> name for any valid user identity. For some authentication providers, this
> might be implemented as a query. For others, it might involve maintaining a
> cache that is populated as users use the Broker.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
