SAML Authentication Returns HTTP 405 Error on Jetty
search cancel

SAML Authentication Returns HTTP 405 Error on Jetty

book

Article ID: 429034

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

After migrating the Automic Web Interface (AWI) from a Tomcat container to a Jetty container, users encounter an HTTP 405 (Method Not Allowed) error during SAML authentication. 

Error message:

HTTP ERROR 405 HTTP method POST is not supported by this URL

Environment

CA Automic Workload Automation - Automation Engine: 24.x

Cause

The issue is caused by a case-sensitivity mismatch between the Service Provider (SP) URL defined in the Automic system and how the Jetty web server handles the URL path.

In this specific scenario:

  • The UC_SAML_SETTINGS were configured with the AWI identifier in uppercase (e.g., https://[hostname]/AWI/).

  • Modern browsers or the Jetty environment may normalize or redirect these requests to lowercase.

  • Because the SAML assertion was expected at a case-specific endpoint that did not match the request, the server rejected the method, resulting in the HTTP 405 error.

Resolution

To resolve this, ensure that the case used in your SAML settings matches the actual URL path used by the application container.

  1. Log into the relevant Client (usually Client 0).

  2. Open the UC_SAML_SETTINGS VARA object.

  3. Locate the SP_ENTITY_ID or the endpoint URL entries.

  4. Update the AWI reference from uppercase to lowercase (e.g., change AWI to awi).

  5. Save the object and restart the AWI or refresh the configuration.