Support Certificate Authentication

[RASakach]

Many Zowe customers configure certificates for authentication of service ids and have indicated that the industry is likely to transition to require certificates for all user authentication. We have a large financial customer requesting that all Zowe clients support certificate authentication. Zowe CLI supports this, we need to ensure Zowe Explorer (VS Code) supports this as well.

Tasks

Preview Give feedback

1. Implement certificate authentication support for API ML #3366
   enhancement priority-medium +2
   

   
2. Support APIML login with PEM certificates #2802
   +0
   

   
3. Provide Client Side z/OSMF Certificate Support Zowe Explorer #2373
   community-upvoted enhancement priority-high +3
   
4. Document certificate authentication in Zowe Explorer #3444
   On-Hold docs enhancement priority-medium +4
   

[github-actions]

Thank you for raising this enhancement request.
The community has 90 days to vote on it.
If the enhancement receives at least 10 upvotes, it is added to our development backlog.
If it receives fewer votes, the issue is closed.

[adam-wolfe]

Related to #2373, though I think the intention with this issue is to support use of certificates to authenticate to the APIML and generate and store a token for the user.

[github-actions]

Thank you for raising this enhancement request.
The community has 90 days to vote on it.
If the enhancement receives at least 10 upvotes, it is added to our development backlog.
If it receives fewer votes, the issue is closed.

[JillieBeanSim]

only API ML support complete reopening for direct connect work

[traeok]

Referring back to this comment, should we track the z/OSMF / direct connect support in #2373 instead and mark this as complete? From my understanding, 2373 is for tracking the direct connect support and this issue was meant to track API ML support.

[JillieBeanSim]

Referring back to this comment, should we track the z/OSMF / direct connect support in #2373 instead and mark this as complete? From my understanding, 2373 is for tracking the direct connect support and this issue was meant to track API ML support.

Hey @traeok the title & description of this issue doesn't mention API ML or direct connect, it just requests cert support. The other may have been created to break this story apart where the API ML support was covered by one issue and direct connect by another. I believe that could make this issue an epic, what do you think?

[traeok]

Sorry for the delay @JillieBeanSim - I agree that the issue doesn't exclusively reflect API ML support, so we could turn this into an epic. I feel that we should still track the API ML work under its own issue as it was already completed. We could track the z/OSMF direct connect in #2373, and I can make a separate issue for API ML & assign it to the merged PR 👍