Layer7 API Management

Expand all | Collapse all

{"httpStatusCode":404,"errorCode":505,"devErrorMessage":"tenant id +server host name not found","userErrorMessage":"tenant id +server host name not found.","locale":"en","userErrorKey":"error.resource.not.found"}

  • 1.  {"httpStatusCode":404,"errorCode":505,"devErrorMessage":"tenant id +server host name not found","userErrorMessage":"tenant id +server host name not found.","locale":"en","userErrorKey":"error.resource.not.found"}

    Posted 03-02-2021 06:43 PM
    Hi,

    When i tried to access api portal environment . I am getting below error. Can somebody help to resolve this.
    Error: {"httpStatusCode":404,"errorCode":505,"devErrorMessage":"tenant id +server host name not found","userErrorMessage":"tenant id +server host name not found.","locale":"en","userErrorKey":"error.resource.not.found"}


  • 2.  RE: {"httpStatusCode":404,"errorCode":505,"devErrorMessage":"tenant id +server host name not found","userErrorMessage":"tenant id +server host name not found.","locale":"en","userErrorKey":"error.resource.not.found"}

    Posted 03-04-2021 02:55 PM
    Hello, how r u?

    To access the API Portal you need to have on your DNS Server or host file an entry containing tenant_id.domain.xpto pointing to the server's IP. For example, for a portal under broadcom domain configured with a tenant = portal, the hostname for access would be portal.broadcom.com.

    If you are trying to access the server via a browser directly by IP, without the hostname, know that this is not possible because the application uses the hostname to define which tenant should be loaded in the browser.

    Regards

    ------------------------------
    Sec4you
    ------------------------------



  • 3.  RE: {"httpStatusCode":404,"errorCode":505,"devErrorMessage":"tenant id +server host name not found","userErrorMessage":"tenant id +server host name not found.","locale":"en","userErrorKey":"error.resource.not.found"}

    Broadcom Employee
    Posted 03-05-2021 06:35 PM
    Hi:

    Exactly right Rogerio!  Check that the tenant name you created exactly matches what hits the portal and is not proxied to some other name at a loadbalancer.  Sometimes I get the question the application architecture is designed this way and the reason is that is a SaaS type architecture, even for on-premise so you can have several tenants on the same portal referenced by different URL's customer facing.  It actually works quite well for many customers with different partners.

    Let us know if it works for you and have a good weekend.

    Alex.

    ------------------------------
    Solution Architect - Security & Integration
    Symantec Enterprise Division, Broadcom Inc.
    Vancouver, B.C. Canada
    ------------------------------