Zowe - ZWEAG104E Authentication service is not available at URL
search cancel

Zowe - ZWEAG104E Authentication service is not available at URL

book

Article ID: 409957

calendar_today

Updated On:

Products

Zowe

Issue/Introduction

ZWESVUSR ERROR (o.z.a.g.s.s.z.ZosmfService) ZWEAG104E Authentication service is not available at URL 'protocol://WWW.EXAMPLE.COM:PORT/zosmf/info'

I/O error on POST request for'protocol://WWW.EXAMPLE.COM:PORT/zosmf/services/authenticate": Connect to'protocol://WWW.EXAMPLE.COM:PORT/zosmf/info' failed: EDC8128I  Connection refused

Environment

Zowe 

Resolution

Do some checks to your system first:

  1. Check if z/OSMF is up running. The default job name of z/OSMF is IZUSVR1 and IZUANG1.
    1. Take a look at the JES2 job list.
  2. Check if z/OSMF is accessible at the specified URL .You can use  your web browser.
    1. Visit the protocol://www.example.com/zosmf in your browser (the computer must have access to the LPAR). If it is accessible, you should see a big "Welcome to z/OS" logo.
  3. Call z/OSMF using cURL from the ZOWE package (run curl command in the USS of ZOWE Lpar)
    1. For ZOWE v2:
      • node   <zowe_dir>/bin/utils/curl.js  -k -H "X-CSRF-ZOSMF-HEADER: true"  protocol://www.example.com:PORT/zosmf/info
    2. For ZOWE v3:
      • curl  -k -H "X-CSRF-ZOSMF-HEADER: true"  protocol://www.example.com:PORT/zosmf/info

If z/OSMF is accessible, you should see something similar to the following:

{"zos_version":"05.29.00","zosmf_port":"port number","zosmf_version":"29","zosmf_hostname":"your domain","plugins":...

If you cannot see this but you are sure z/OSMF is running, you will need to ask your system administrator for help. Maybe a firewall or a network policy facility (e.g., pagent) is blocking traffic to the PORT.

Additional Information

In addition to running curl command within the ZOWE server, users can test APIML login functionality using the API Gateway Swagger "Try it out" feature. The relevant endpoint is /auth/login using the POST method.

If a user successfully authenticates through the endpoint using TSO credentials and receives a 204 Authorized status via API Gateway Swagger, but then encounters a 503 Service Unavailable error when running the "zowe auth li apiml" command from a client machine, it is likely a network issue.

This behavior suggests that a firewall or another network restriction is blocking the connection between the client machine and the Zowe server.