Hari

Actually we depend on a different project https://github.com/nestjs/nest/tree/master/packages/platform-express which depends on older version of this project.. I can ask them too but they may not agree to use a rc...

@rnewson thats great.. are you expecting more changes on the master? And will the new changes be made available as a release?

@balhar-jakub This is different from what is being done for api layer version 3. This is for version 2 where the request is to replace Javax dependencies with Jakarta 8...

zaas client also seems to have similar issue with processing safkeyring https://github.com/zowe/api-layer/blob/15c887c1ed264f065fb5b1a1f731508997841039/zaas-client/src/main/java/org/zowe/apiml/zaasclient/service/internal/ZaasHttpsClientProvider.java#L131-L137 

@achmelo I am confused why four slashes are required. Other configuration seem to allow 2 slashes like below on. https://techdocs.broadcom.com/us/en/ca-mainframe-software/traditional-management/ca-common-services-for-z-os/15-0/installing/complete-configuration-tasks/perform-post-deployment-tasks/configure-apache-tomcat-to-use-ssl-with-keyrings.html That this documentation by IBM seems to have a different...

or this one in IBM FAQs https://public.dhe.ibm.com/software/Java/Java11/IBMJCECCA/zJavaSecurityFAQ.html#cca_q07a 

Any update?

@taban03 I am not sure what is being asked.. I think apiml code should set the required properties before processing keyring string… provider could be determined by store type…

> We plan to fix it, It's acknowledged as a bug and the expectation is that the fix will be either in 2.5 or 2.6 version of Zowe. Any ETAs...

@taban03 I know what zowe asks currently… I was just suggesting that the requirement can be removed…