Previous Topic: HTTP Error Handling for SAML 2.0 AuthenticationNext Topic: Configure Request Processing with a Proxy Server at the SP


Request Processing with a Proxy Server at the SP

When SiteMinder receives certain requests at the SP, it validates the message attributes. SiteMinder verifies the attributes using the local URL for Federation Web Services application. After verification, SiteMinder processes the request.

For example, a logout request message can contain the following attribute:

Destination=”http://sp.domain.com:8080/affwebservices/public/saml2slo”

In this example, the destination attribute in the logout message and the address of the Federation Web Services application are the same. SiteMinder verifies that the destination attribute matches the local URL of the FWS application.

If the SiteMinder sits behind a proxy server, the local and destination attribute URLs are not the same. The destination attribute is the URL of the proxy server. For example, the logout message can include the following destination attribute:

Destination=”http://proxy.domain.com:9090/affwebservices/public/saml2slo”

The local URL for Federation Web Services, http://sp.domain.com:8080/affwebservices/public/saml2slo, does not match the Destination attribute so the request is denied.

You can specify a proxy configuration to alter how SiteMinder determines the local URL used for verifying the message attribute of a request. In a proxy configuration, SiteMinder replaces the <protocol>://<authority> portion of the local URL with the proxy server URL. This replacement results in a match between the two URLs.