Junction filtering issues for the ACTION URL

The login page served by a response handler located on a junctioned server is filtered by WebSEAL when it is returned to the client over the junction. The page might contain a FORM tag similar to WebSEAL's standard static HTML login response page (login.html):

<FORM METHOD=POST ACTION="/pkmslogin.form">

If this FORM tag appears in a page served by a remote response handler located on a junctioned server, WebSEAL filters the server-relative ACTION URL by prepending the junction name to the path:

/jct/pkmslogin.form

Because the pkmslogin.form authentication handler is local to WebSEAL, WebSEAL cannot find the filtered version of the URL and the request for an authentication operation from WebSEAL fails.

We must ensure the response handler serves a login page with an ACTION attribute that correctly points to pkmslogin.form. Use a relative path expression to navigate upwards from the location where the custom login page is served. For example, if the login page is served from the following JSP (JavaServer Pages) application:

/jct/redirect-app/custom-login.jsp

the ACTION URL in this page must be expressed as follows:

<FORM METHOD=POST ACTION="../../pkmslogin.form">

WebSEAL does not filter relative path names. Therefore, this path is correctly resolved by the client browser as being located in the document root space of the WebSEAL server.

For complete information about WebSEAL filtering rules, see Filter rules for tag-based static URLs.

Parent topic: Remote response handling with local authentication