-
Type: Story
-
Status: Closed (View Workflow)
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 2.0
-
Fix Version/s: 2.2 Penguins
-
Labels:None
-
Sprint:2.2 Penguins
As a User I'd like to be able to log in to Antarcticle without warring about case of the letters so that it's easier to log in.
Acceptance Criteria
- In case there is already a single user in Antarcticle internal DB, then the username is treated in case-insensitive manner
- In case user is absent in Antarcticle internal DB, then Antarcticle should send authentication request to Poulpe and, if the request is successful, then user should be stored in Antarcticle DB without the loss of letter case
- If there is a single user in Antarctilce, but authentication failed, then request to Poulpe is send for authentication with exact data as was input in the log in form.
- If user was authenticated successfully by Poulpe and the user in the response is exactly the same as in internal DB, then its password should be updated in Antarcticle DB
- If user was authenticated successfully by Poulpe but the returned user is in different case, then Antarcticle should store additional user with different case in username.
The rest of authentication process stays the same - if user is not authenticated by Poulpe, then Antarcticle should respond with the error to user and the data should be not updated in Antarcticle DB.
- is blocked by
-
POULPE-521 Case-insensitive authentication in Poulpe
- Closed
- is duplicated by
-
ANTARCTICLE-243 Case-insensitive username while login
- Closed
- relates to
-
POULPE-522 REST api performs case-sensitive comparison for password hash
- Open
-
ANTARCTICLE-303 User can login with old password after changing
- Closed
-
JC-1824 Case-insensitive authentication in JCommune via Poulpe
- Open
- Testing discovered
-
POULPE-523 REST API: Authentications returns not correct username
- Closed