z/OSMF onboarding shows incorrect SSO and API base path in Zowe v3.2
Open
@hrishikesh-nalawade is already working on this.
Since Jan 7, 2026.
bug
Priority: High
size/S
- Dominant language
- Java
- Stars
- 92
- Forks
- 81
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 46
Description
Describe the bug
Zowe v3.2 the z/OSMF service is showing incorrect metadata in the Swagger page:
SSO: not supported (Expected: supported)
API Base Path: /ibmzosmf/api/{api-version} (Expected: /ibmzosmf/)
The same configuration and system setup work correctly with Zowe v3.1, where SSO is detected and the base path is displayed correctly.
Steps to Reproduce
RD v3.2 is running with the issue
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.