AT-TLS with server enabled but client disabled has wrong registration
Open
Nobody has claimed this yet.
bug
Priority: High
size/S
V3
- Dominant language
- Java
- Stars
- 92
- Forks
- 81
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 46
Description
Describe the bug
Gateway registers to DS as HTTP only with zowe settings server.tls.attls: true and client.tls.attls: false.
It should register as https in this scenario.
Expected behavior
Registers as HTTPS so other clients who read the DS registry know how to connect to it (without outbout rules in AT-TLS)
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.
Research direction
Trace the gateway's registration with DS and inspect how server.tls.attls and client.tls.attls are handled. Verify the behavior for server.tls.attls: true with client.tls.attls: false; done means the gateway registers as HTTPS so clients reading the DS registry can connect without outbound AT-TLS rules.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100