Opened 13 years ago

Closed 12 years ago

Last modified 12 years ago

#156 closed enhancement (fixed)

Allow users to set/modify friendly name

Reported by: twagoo Owned by: twagoo
Priority: minor Milestone:
Component: ComponentRegistry Version:
Keywords: Cc:


Now the user's 'friendly' name (in contrast to id provided by IdP) is taken from CN or DisplayName? if available when the user is created into the database. If no name is available or if it has to be changed for some reason, this cannot be done. For this a simple interface can be designed that sends a new display name for the currently logged in user to the REST service.
This name should also be shown in the top right part of the screen instead of the eppn/persistent_id if available.

Notifiy Torsten Compart <> when fixed

On 12/10/11 14:02 , Torsten Compart wrote:

Hi Dieter,

after an internal discussion about the attributes of our IDP send to the
component register. You said, that 'eppn' (eduPersonPrincipalName) would
be required. This would mean, that the Component Register uses an
attribute which is the authentication token of the whole CLARIN network
used for every other SP too. We could provide the less explicit
attribute 'persistent_id' (eduPersonTargetId), which would be generated
by our IDP only for the Component Register. I think for the purpose of
the Component Register this would be enough. Would it be enough to
release the attribute 'persistent_id' for a successful authentication?
This would help to clear the discussion with our data protection officer.

Hi Torsten,

I think that should be sufficient. It means however that we need to make
some changes to the implementation of the Component Registry in that it
queries the user to provide a "human readable" name after logging in
when eppn or displayname is not available. I think you can tell your
data protection officer that we can live with that solution.

It might take some time on the other hand before you really can login at
the component registry. I'm cc'ing Twan, he can add you to the ticket
for this so that you get a signal as soon as eptid is supported.

Change History (6)

comment:1 Changed 12 years ago by dietuyt

Giving this a bump, as more and more "unreadable" users are appearing in the ComponentRegistry.

comment:2 Changed 12 years ago by twagoo

r1779,r1789:1790,r1792:1793 implement the following:

  • when a user registers a new component/profile, the display name from the database is used in the description
  • a page '/admin/userSettings' has been added that allows an authenticated user to modify their display name
  • in the Flex UI, next to the user name when logged in, a link to this user settings page is shown

comment:3 Changed 12 years ago by twagoo

Priority: majorminor

Showing the display name as a label for the user currently logged in (the one in the top right corner) is going to be a bit more tricky because currently this is the value of the remoteUser environment variable, passed to the Flex UI without much intervention. It can be done but it requires quite some refactoring.

Leaving this ticket open, lowering priority.

comment:4 Changed 12 years ago by twagoo

test, excuus

comment:5 Changed 12 years ago by twagoo

Resolution: fixed
Status: newclosed

Created new ticket #188 for the case of the name in top-right corner

comment:6 Changed 12 years ago by twagoo

Added 'close tab' link (which says 'Back to Component Registry') to settings page in r1984

Note: See TracTickets for help on using tickets.