As a system administrator, I want to allow the "at" symbol (@) in usernames

Description

(Discussion of this issue has changed its direction and description has been updated, in case comment thread doesn't quite seem to follow.)

Many users want or expect to be able to use @ symbols in their usernames, most typically so they can use their email address as their username.

Current behavior in the system: If you attempt to create a username with an "@" symbol in the staff interface, you'll get a message that the user was not created when you attempt to save that record. It would be better if a specific message displayed alerting the user to the issue. (This bug was reported at the UVA ArchivesSpace workshop.)

Complexity

None

Attachments

2

Activity

Show:

Jared CampbellMarch 11, 2019 at 7:06 PM

Was able to create a user w/ @ in the username. Tested in test.archivesspace.org

Joshua ShawMarch 5, 2019 at 7:20 PM

The tooltip has been updated and I was able to create a user with an '@' in the username. Tested in test.archivesspace.org

Lydia TangFebruary 2, 2018 at 4:24 PM

Do you know if enabling a username with an @ symbol (such as a work email address) would lead to any potential issues?

Jason LoefflerFebruary 1, 2018 at 10:20 PM

The consensus was to move forward with this. The specification is to include a tooltip that reads:

"Permitted characters include a-z, A-Z, numbers, hyphen, dash, and dot."

There was some discussion on whether to allow an @, such as institutions wishing to use email addresses. If that's still desired I recommend hashing and/or salting stored email addresses, since the security perimeter of ArchivesSpace is very much a work in progress.

That's an architectural/security decision I'll leave up to smarter people. Otherwise, this is ready to be implemented.

Lydia TangJanuary 29, 2018 at 5:20 PM

Any developments with this?

Done

Details

Assignee

Reporter

Affects versions

Priority

Harvest Time Tracking

Open Harvest Time Tracking

Created March 1, 2017 at 8:01 PM
Updated May 30, 2019 at 12:39 PM
Resolved May 30, 2019 at 12:39 PM
Harvest Time Tracking