Search
K

Troubleshoot runtime issues

Runtime issues may occur after Maverics successfully starts-up. Typically, runtime issues are caused by misconfiguration, down dependent systems, and overloaded host machines.

HTTP 400 Bad Request

Symptoms

User sees an error message in the browser with verbiage related to a 400 status code immediately after logging in, and before accessing the application.

Remediation

Support Center

Capture the error message in the browser if there is one and then contact a Maverics administrator for further troubleshooting.

Maverics Admin

If an error message was provided, determine if the issue is related to the Fabric configuration or the authentication flow between the Maverics module and Orchestrator. If no error message was provided, review the Maverics logs.

HTTP 403 Unauthorized

Symptoms

User sees a 403 unauthorized error message in the browser and believes they should have access to a web resource.

Remediation

Support Center

Ask the user to clear their browser cache, and to retry accessing the resource. If that does not resolve the issue, contact a Maverics administrator for further troubleshooting.

Maverics Admin

Confirm dependent attribute stores are up. Downed LDAP servers or databases may impact a user's ability to authorize.
Review the corresponding App Gateway policies and validate whether the affected user(s) should have access.

HTTP 404 page not found

Symptoms

User sees a 404 page not found message in the browser and has recently accessed the web resource successfully.

Remediation

Support Center

Capture the requested URL and confirm with application owners that the web resource is valid. If the requested resource should be valid, contact a Maverics administrator for further troubleshooting.

Maverics Admin

Validate that an App Gateway is defined for the requested resource on the web server's configuration file and on the Orchestrator's configuration file.

HTTP 500, HTTP 502, HTTP 503, HTTP 504

Symptoms

User cannot successfully load the web resource of interest or is not getting a response.

Remediation

Support Center

Capture any output written to the browser. Contact application owners to determine if the app is in a known unhealthy state. Engage Maverics administrators if the app team believes the error is related to Maverics or authentication/authorization.

Maverics Admin

Review both web server logs and Orchestrator logs to further diagnose the issue.

Unexpected Application Experience

Symptoms

User is able to login to an application but doesn't see their name or other expected profile attributes.

Remediation

Support Center

Document the unexpected behavior and the user's profile attributes that are missing or not correct. Connect with the app team to determine whether they also believe the behavior is unexpected. Contact a Maverics administrator for further troubleshooting if the app team believes profile attributes are not being sent as HTTP headers.

Maverics Admin

Confirm dependent attribute stores are up. Downed LDAP servers or databases may impact the ability to build a user's profile.
Confirm the correct set of headers that the application is expecting are defined in the corresponding App Gateways.