Skip to content

CMLDEV-1740 Treat 401 login failure as InitializationError - #264

Merged
tmikuska merged 1 commit into
devfrom
CMLDEV-1740-accept-401-login-failure
Oct 13, 2026
Merged

tmikuska merged 1 commit into
devfrom
CMLDEV-1740-accept-401-login-failure

Conversation

@tmikuska

@tmikuska tmikuska commented Oct 5, 2026

Copy link
Copy Markdown
Collaborator

Controllers >= 2.11 return 401 (not 403) for every login failure. Pick the login-failure status from the controller version (401 for

= 2.11, 403 before) and raise InitializationError for it regardless
of the auth method (username/password or preset JWT). The message is now credential-neutral: 'Unable to authenticate, please check your credentials'.

@tmikuska tmikuska self-assigned this Oct 5, 2026
@tmikuska
tmikuska force-pushed the CMLDEV-1740-accept-401-login-failure branch 4 times, most recently from 08e8694 to 04b9012 Compare October 7, 2026 22:42
Controllers >= 2.11 return 401 (not 403) for every login failure. On
2.11+, a 401 from the POST authenticate call raises InitializationError;
a 401 from any other request (expired/revoked preset JWT or PAT) still
raises APIError, so token expiry keeps failing loudly. Controllers
before 2.11 keep the 403 rule. The message is now credential-neutral:
'Unable to authenticate, please check your credentials'.
@tmikuska
tmikuska force-pushed the CMLDEV-1740-accept-401-login-failure branch from 04b9012 to f5b06ba Compare October 13, 2026 09:50
@tmikuska
tmikuska merged commit a1ba990 into dev Oct 13, 2026
5 checks passed
@tmikuska
tmikuska deleted the CMLDEV-1740-accept-401-login-failure branch October 13, 2026 10:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant