Best practices: Header apps
The most common Access Gateway integration involves legacy Web Access Management (WAM) apps based on values contained in request headers.
Here are some attributes of WAM solutions:
- They may be custom-built or third-party solutions like Oracle Access Manager, CA Siteminder, or others.
- They rely on header attributes for SSO.
- They're often deployed behind proxy web-servers like Apache.
- They involve validating app header contents before testing with back-end protected web resources.
When configuring an app for header-based SSO, make sure you review the steps to place the app behind a proxy server. Many Access Gateway troubleshooting situations arise not from SSO but because the app was incorrectly configured for a proxy server.
Review attribute requirements
Before integrating any header-based app examine all required and expected header elements. Ensure that the app definition in Access Gateway includes all required attributes.
About apps that Apache HTTP Server previously served
In situations where protected web resources that Apache HTTP Server previously served, Apache HTTP Server may have added header elements to requests before they were forwarded.
The Apache mod_header file often defined all required header fields and can be used as a source of information for expected header content.
Proxy and load balancers
Many apps use the terms web proxy and load balancer interchangeability. Examine any documentation related to web proxies, load balancers, and related content to determine the value requirements of the app attribute.