Usernames for authenticatedUsers that are not also BuiltIn are not subject to same username validation
Open
Nobody has claimed this yet.
Feature: Account & User Info
Type: Bug
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
Noticed in passing that a Shibboleth user with an email of the format foo+bar@example.org will end up with a user identifier of foo+bar; which is inconsistent with the existing regex for usernames.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how Shibboleth users receive their identifiers and where username validation is applied to authenticated users that are not BuiltIn. Compare that path with the existing username regex and add regression coverage for an identifier such as foo+bar; done means the same validation applies consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100