Skip to content

[TECH] Utiliser une 401 plutôt qu'une 403 en cas d'erreur de mot de passe dans la page de connexion à l'espace surveillant (PIX-17461). #12029

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@ const sessionDomainErrorMappingConfiguration = [
},
{
name: InvalidSessionSupervisingLoginError.name,
httpErrorFn: (error) => new HttpErrors.ForbiddenError(error.message, error.code),
httpErrorFn: (error) => new HttpErrors.UnauthorizedError(error.message, error.code),
},
].map((domainErrorMappingConfiguration) => new DomainErrorMappingConfiguration(domainErrorMappingConfiguration));

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -107,7 +107,7 @@ describe('Unit | Certification | Session | Application | HttpErrorMapperConfigur
const error = httpErrorMapper.httpErrorFn(new InvalidSessionSupervisingLoginError());

// then
expect(error).to.be.instanceOf(HttpErrors.ForbiddenError);
expect(error).to.be.instanceOf(HttpErrors.UnauthorizedError);
expect(error.message).to.equal(SESSION_SUPERVISING.INCORRECT_DATA.getMessage());
expect(error.code).to.equal(SESSION_SUPERVISING.INCORRECT_DATA.code);
});
Expand Down