Broadcom Mainframe Software Community

 View Only
  • 1.  VSCode with Zowe Extension - Login via MFA

    Posted Jun 02, 2024 10:09 PM

    Hello,

    New to VSCODE and ZOWE Extension and logon via MFA (token number generated).

    Question,

    How to clear or ask VSCode not to save the MFA token number when accessing Mainframe.

    Thanks.



  • 2.  RE: VSCode with Zowe Extension - Login via MFA

    Broadcom Employee
    Posted Jun 03, 2024 11:39 AM

    The word "token" is used in a couple of contexts within the Zowe clients. Since your question mentions MFA, I think your reference is to a short-term (30 second) generated password.

    Zowe client support for MFA is only accomplished through the use of the API Mediation Layer (APIML) server component of Zowe. Your zowe.config.json configuration file must be configured to use APIML. In that context, when Zowe Explorer asks you to login, you supply your user name and your 30-second password. ZE does not store either your user name or 30-second password. Instead, it uses those credentials to login to APIML, which returns an APIML long-lived token. The duration of that token can be configured in your mainframe APIML configuration, but an 8 hour duration is a common example.

    ZE automatically stores the APIML token into the client-side secure credential store. ZE then passes that APIML token on all future REST requests to your mainframe server. Tomorrow, when you start work again, you would typically login to APIML again for the day.




  • 3.  RE: VSCode with Zowe Extension - Login via MFA

    Broadcom Employee
    Posted Jun 03, 2024 11:41 AM

    The word "token" is used in a couple of contexts in the Zowe clients. Since your question mentions MFA, I think your reference is to a short-term (30 second) generated password.

    Zowe client support for MFA is only accomplished through the use of the API Mediation Layer (APIML) server component of Zowe. Your zowe.config.json configuration file must be configured to use APIML. In that context, when Zowe Explorer asks you to login, you supply your user name and your 30-second password. ZE does not store either your user name or 30-second password. Instead, it uses those credentials to login to APIML, which returns an APIML long-lived token. The duration of that token can be configured in your mainframe APIML configuration, but an 8 hour duration is a common example.

    ZE automatically stores the APIML token into the client-side secure credential store. ZE then passes that APIML token on all future REST requests to your mainframe server. Tomorrow, when you start work again, you would typically login to APIML again for the day.