Skip to content
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.

Sign up for GitHub

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

Jump to bottom

AT-TLS with server enabled but client disabled has wrong registration #4042

Open
pablocarle opened this issue Mar 21, 2025 · 0 comments
Open

AT-TLS with server enabled but client disabled has wrong registration #4042

pablocarle opened this issue Mar 21, 2025 · 0 comments
Labels
bug Verified defect in functionality Priority: High size/S

Comments

@pablocarle
Copy link
Contributor

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)
@pablocarle pablocarle added bug Verified defect in functionality new New issue that has not been worked on yet labels Mar 21, 2025
@EvaJavornicka EvaJavornicka added size/S Priority: High and removed new New issue that has not been worked on yet labels Apr 2, 2025
@balhar-jakub balhar-jakub moved this from New to Unplanned Bugs in API Mediation Layer Backlog Management Apr 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Verified defect in functionality Priority: High size/S
Projects
API Mediation Layer Backlog Management
Status: Unplanned Bugs
Milestone
No milestone
Development

No branches or pull requests
2 participants
@pablocarle @EvaJavornicka