Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Categories Runtime
Created by Guest
Created on Jan 25, 2023

Allow a CWS Web call to specify not to use MASSL

We have a CICS application calling z/OS Connect and wants to use Basic Auth over SSL. When z/OS Connect receives the requests, it asks CICS for a MASSL cert, and CICS obliges by sending the default cert on the ring, which in his case is not the authority we want to use. The request fails because the authority on the cert is not authorized for zOS Connect. The WEB Converse calls specifies BasicAuth with a userid and password, and this is the authority we want to use.

Not using SSL is not an option because the password is only base64 encoded and must be encrypted.

I've searched the doc and it's not clear. For example:

"If you use a URIMAP definition but do not specify a certificate label, the default certificate defined in the key ring for the CICS region user ID is used."

https://www.ibm.com/docs/en/cics-ts/5.6?topic=support-cics-as-http-client-authentication-identification

This indicates to me that the default cert is only sent if you used a URIMAP without a label?


But I also understand that a server (in this case zOS Connect) might require a cert. We've submitted an Idea also to z/OS connect asking for an option that allows a fall back to basic auth without requiring a massl cert - ZCEE-I-449.




Idea priority Medium
  • Guest
    Reply
    |
    Jan 27, 2023
    Closing as per customer request
  • Guest
    Reply
    |
    Jan 27, 2023

    Yes, I'll bring this back to our z/OS Connect team. They told me that they configured it to request MASSL first, and if no certificate drop down to Basic Auth. I guess that's not an option. They've opened an Idea to z/OS Connect about this as well. Please close this.

  • Guest
    Reply
    |
    Jan 27, 2023
    CICS Development: The client doesn't get to pick the authentication mechanism. That is set in the server. In this case the z/OS Connect server must have been configured to require a client certificate to be provided. CICS responded to the request by sending the default certificate from the keyring, which then failed.

    The solution is to either configure the server correctly so that it does not require a client certificate for an inbound TLS connection (set clientAuthentication="false" in the <ssl> configuration element in the z/OS Connect server.xml file) or provide a suitable certificate and name it on the URIMAP definition

    Does this address your question ?