Login via APIML gateway returns ZWEAG120E instead of ZWEAT412E for expired password using auth zosmf
@pavel-jares-bcm is already working on this.
Since May 14, 2025.
- Dominant language
- Java
- Stars
- 92
- Forks
- 81
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 46
Description
Attempt to login to API ML /gateway/api/v1/auth/login endpoint using an expired password returns message ZWEAG120E (invalid username or password) instead of ZWEAT412E (expired password).
Steps to Reproduce
Get a hold of account whose password just expired (but new one has not been set).
Issue login POST request to /gateway/api/v1/auth/login using the expired password.
Get a response with message number ZWEAG120E
Expected behavior
The response should be ZWEAT412E for logins with expired password.
Details
Version 2.18.0
Test environment: z/OS 2.5.0
Additional context
When attempting to login through API ML gateway with expired password, we want to be able to tell the client, the issue is the expired password and not an invalid one.
If you uses saf the problem is solved but with zosmf is not correct yet. There's a plan route to modify this feature for installations with auth zosmf?
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.
Assessment
This issue has not been assessed yet.