Zowe

Zowe

Zowe

Zowe is an open source project created to host technologies that benefit the Z platform from all members of the Z community

 View Only

  • 1.  Can't login to ZOWE Desktop! Authentication failed for 3 types. Types: ["saf","apiml","zss"]

    Posted Wed April 26, 2023 07:49 AM
    Edited by Shameera Ismail Thu April 27, 2023 02:32 AM

    Hi, This post is moved to ZOWE Community.. thanks



  • 2.  RE: Can't login to ZOWE Desktop! Authentication failed for 3 types. Types: ["saf","apiml","zss"]

    Posted Wed April 26, 2023 07:54 AM

    Shameera - this is not a good forum to do debug work - if you are using the Zowe Desktop with an IBM product that requires it - please open a case with the product team (Like OMEGAMON, Db2 DevOps, Db2 or IMS Admin Foundation). My other suggestion would be to review zowe.org documentation and join the open community slack channels for assistance. 



    ------------------------------
    Bruce Armstrong
    Offering Manager on Zowe Open Source Project
    IBM
    RTP NC
    armstrob@us.ibm.com
    ------------------------------

    Original Message


  • 3.  RE: Can't login to ZOWE Desktop! Authentication failed for 3 types. Types: ["saf","apiml","zss"]

    Posted Thu April 27, 2023 02:33 AM
    Edited by Shameera Ismail Thu April 27, 2023 03:25 AM

    Hi Bruce,

    Thanks, done.. was searching for Zowe community and ended up with this link





    Original Message


  • 4.  RE: Can't login to ZOWE Desktop! Authentication failed for 3 types. Types: ["saf","apiml","zss"]
    Best Answer

    Posted Thu April 27, 2023 10:44 AM

    Hi Shameera,

     

    The problem is likely because of the certificate that z/OSMF is using which is not being trusted by Zowe.  Can you change the `zowe.verifyCertificates: ` value to be `DISABLED`. 

     

    Best regards,

     

    Joe Winchester

    Zowe.org Leadership Committee Member  - IBM Senior Technical Staff Member - Open Mainframe Project Ambassador

     

    Phone: 44-7749-965423

    Twitter: @JoeWinchester    LinkedIn: joewinchester

    Unless otherwise stated above:

    IBM United Kingdom Limited
    Registered in England and Wales with number 741598
    Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU



    Original Message


  • 5.  RE: Can't login to ZOWE Desktop! Authentication failed for 3 types. Types: ["saf","apiml","zss"]

    Posted Fri April 28, 2023 01:23 PM

    Hi Joe, 

    Thank you very much, that worked! 



    ------------------------------
    Shameera Ismail
    ------------------------------

    Original Message


  • 6.  RE: Can't login to ZOWE Desktop! Authentication failed for 3 types. Types: ["saf","apiml","zss"]

    Posted Fri May 05, 2023 09:21 AM
    Edited by Shameera Ismail Mon May 08, 2023 10:45 AM

    Hi Joe, Good Day

    Just curious about the issue. 

    I tried with NONSTRICT, and got the same issue again.

    NONSTRICT: will validate if the certificate is trusted in our trust store.   #  This mode does not validate certificate Common Name and Subject   #   Alternative Name (SAN).

    It only works with option ' DISABLED ' .

    z/OSMF and Zowe has the same root & intermideate do we still have to try connecting the z/OSMF Certificate to Zowe Keyring ?

     just want to know if I missed any thing..

    Thanks,



    ------------------------------
    Shameera Ismail
    ------------------------------

    Original Message


  • 7.  RE: Can't login to ZOWE Desktop! Authentication failed for 3 types. Types: ["saf","apiml","zss"]

    Posted Tue May 09, 2023 03:30 PM

    Hi Shameera,

    If z/OSMF and Zowe have the same root and intermediate, then you should be able to use STRICT as long as you have both of the CERTAUTHs in your Zowe keyring.    Make sure also that you have them both defined in the pem section of the zowe.yaml, with a `-` separator.    See the issue https://github.com/zowe/docs-site/issues/1550 where another customer ran into a similar problem with intermediate and root CA and the pem section.

    If the CERT and CERTAUTH are in the keyring and all correct, then all that the NONSTRICT does is drop the SAN check.   This is useful because some  mainframe shops tend to create valid certs for one LPAR TCP/IP stack and copy it to another to test it (which fails a SAN check) before using it with the right cert on the right LPAR.  This avoids the need to issue a new CERT with the right SAN for the test LPAR.

    Let us know how you get on.



    ------------------------------
    Joe Winchester
    Hursley
    ------------------------------

    Original Message


  • 8.  RE: Can't login to ZOWE Desktop! Authentication failed for 3 types. Types: ["saf","apiml","zss"]

    Posted Wed May 10, 2023 11:08 AM

    Hi Joe, 

    Thank you very much again, it worked.

    https://github.com/zowe/docs-site/issues/1550  this was helpful.

    Shameera I



    ------------------------------
    Shameera Ismail
    ------------------------------

    Original Message


Related Content