Skip to content

Issue with docs.zowe.org/stable/extend/extend-apiml/zowe-api-mediation-layer-security-overview/ #4472

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

Open
colinpaicemq opened this issue May 17, 2025 · 0 comments

Comments

@colinpaicemq
Copy link
Collaborator

Description

It says

Your z/OSMF instance can be enabled to support JWTs as described in Enabling JSON Web Token support. In such cases, the Zowe API ML uses this JWT and does not generate its own Zowe JWT. All authentication APIs, such as /gateway/api/v1/login and /gateway/api/v1/check function in the same way as without z/OSMF JWT. The Gateway service endpoint /gateway/api/v1/auth/keys/public serves the z/OSMF JWK that can be used for JWT signature validation.

Do any of the z/OSMF parameters in

https://www.ibm.com/docs/en/zos/2.4.0?topic=configurations-enabling-json-web-token-support

have to match up with any Zowe ones? It would be good to say

the parameter.... must match the z/OSMF definition..

or

No parameters in https://www.ibm.com/docs/en/zos/2.4.0?topic=configurations-enabling-json-web-token-support need specific values, and the z/OSMF defaults are suitable for Zowe

Pages to Update

Screenshots

Expected behavior

Additional context

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

No branches or pull requests

1 participant