Maximo

 View Only
Expand all | Collapse all

UNABLE_TO_VERIFY_LEAF_SIGNATURE Error when connecting MFA configuration tool to Maximo Manage

  • 1.  UNABLE_TO_VERIFY_LEAF_SIGNATURE Error when connecting MFA configuration tool to Maximo Manage

    Posted Tue December 06, 2022 10:02 AM
    Hi All

    I am getting the below error message when I try to login to MAF Configuration application. I am using the URL of Maximo Manage application (Maximo Manage 8.0.0) and an API to to authenticate. MAF Tools image version is 8.7.40.

    Any suggestions on what certificate need to be configured and how to configure a certificate for a docker image will be appreciated.

    INFO: server/40 on b0be9e74a13ac: caught an error, responding error response (req_id=42271a44-145900-480d-95c2-0a729741f6ce)
    ERROR: server/40 on b0be9e74a13ac: (req_id=42271a44-145900-480d-95c2-0a729741f6ce, status=500, message="unable to verify the first certificate", code=UNABLE_TO_VERIFY_LEAF_SIGNATURE)
    stack: ResponseError: unable to verify the first certificate
    at Object.internalServerError (/graphite/packages/config-server/node_modules/garage-utils/lib/errors.js:36:5)
    at /graphite/packages/config-server/src/server.js:80:20
    at Layer.handle_error (/graphite/packages/config-server/node_modules/express/lib/router/layer.js:52:5)
    at trim_prefix (/graphite/packages/config-server/node_modules/express/lib/router/index.js:261:13)
    at /graphite/packages/config-server/node_modules/express/lib/router/index.js:230:9
    at Function.proto.process_params (/graphite/packages/config-server/node_modules/express/lib/router/index.js:305:12)
    at /graphite/packages/config-server/node_modules/express/lib/router/index.js:221:12
    at Function.match_layer (/graphite/packages/config-server/node_modules/express/lib/router/index.js:288:3)
    at next (/graphite/packages/config-server/node_modules/express/lib/router/index.js:182:10)
    at Layer.handle_error (/graphite/packages/config-server/node_modules/express/lib/router/layer.js:48:12)
    --
    originalError: {
    "code": "UNABLE_TO_VERIFY_LEAF_SIGNATURE"
    }

    ------------------------------
    Jeevan G
    ------------------------------

    #Maximo
    #AssetandFacilitiesManagement


  • 2.  RE: UNABLE_TO_VERIFY_LEAF_SIGNATURE Error when connecting MFA configuration tool to Maximo Manage

    Posted Wed December 07, 2022 08:19 AM
    Are you using self-signed certificates for your MAS applications? If so, you need to add --env NODE_TLS_REJECT_UNAUTHORIZED=0 when running the docker container. That allows the container to ignore issues with SSL certificates which isn't recommended but is needed for self-signed certificates. 

    I know our version numbering can be confusing since each product has its own version now but can you clarify the Manage version you have actually deployed by getting the System Info from inside of Manage? 8.0 is technically a release we had but it would have been for MAS 8.4 which I assume you're not on at this point. Our most current release is Manage 8.5 for MAS 8.9. The reason this is important is you're using the docker image for MAS 8.7 but there have been some architecture changes between the releases. If you're actually on Manage 8.0 (not 8.4, 8.5, etc.) you might have other issues. 

    ------------------------------
    Steven Shull
    ------------------------------

    Original Message


  • 3.  RE: UNABLE_TO_VERIFY_LEAF_SIGNATURE Error when connecting MFA configuration tool to Maximo Manage

    Posted Mon May 08, 2023 04:35 AM

    Hi Steven,

     

    We are in Maximo 7.6.1.3 version where we installed Maximo Mobile 8.10
    we are getting the similar error. Could you please let us know what to do from certificates perspective?

     

    Client is using purchased certificate they are invoking entrust.

     

    [2023-05-08T08:07:51.014Z]  INFO: server/29 on 1726ba9b564c: received a get request to auth the user (req_id=b16269c6-7af3-4564-9a14-4f13cc161a0c)
    [2023-05-08T08:07:51.019Z]  INFO: server/29 on 1726ba9b564c: whoami is called (req_id=b16269c6-7af3-4564-9a14-4f13cc161a0c)
    [2023-05-08T08:07:51.163Z]  INFO: server/29 on 1726ba9b564c: caught an error, responding error response (req_id=b16269c6-7af3-4564-9a14-4f13cc161a0c)
    [2023-05-08T08:07:51.167Z] ERROR: server/29 on 1726ba9b564c:  (req_id=b16269c6-7af3-4564-9a14-4f13cc161a0c, status=500, code=UNABLE_TO_VERIFY_LEAF_SIGNATURE)
        message: request to XXXXXXXX failed, reason: unable to verify the first certificate
        --
        stack: ResponseError: request to XXXXXXX failed, reason: unable to verify the first certificate
            at Object.internalServerError (/graphite/node_modules/garage-utils/lib/errors.js:36:5)
            at /graphite/packages/config-server/src/server.js:87:20
            at Layer.handle_error (/graphite/node_modules/express/lib/router/layer.js:71:5)
            at trim_prefix (/graphite/node_modules/express/lib/router/index.js:326:13)
            at /graphite/node_modules/express/lib/router/index.js:286:9
            at Function.process_params (/graphite/node_modules/express/lib/router/index.js:346:12)
            at next (/graphite/node_modules/express/lib/router/index.js:280:10)
            at Layer.handle_error (/graphite/node_modules/express/lib/router/layer.js:67:12)
            at trim_prefix (/graphite/node_modules/express/lib/router/index.js:326:13)
            at /graphite/node_modules/express/lib/router/index.js:286:9
        --
        originalError: {
          "message": "request to XXXXXXXXXX failed, reason: unable to verify the first certificate",
          "type": "system",
          "errno": "UNABLE_TO_VERIFY_LEAF_SIGNATURE",
          "code": "UNABLE_TO_VERIFY_LEAF_SIGNATURE"
        }



    ------------------------------
    Meghana Siriveli
    ------------------------------

    Original Message