This chapter contains templates of common configurations. Start with one of our templates and then modify to suit your deployment. Read the summary of each template to find the right match for your application. If you are not sure about the characteristics of your application, start with the basic Application Capture template. This template allows you to setup basic proxying and capture the traffic of the login sequence in a flat file, which will then allow you to analyze the application and subsequently choose the right template or add your own configuration. All templates have the CaptureFilter enabled by default. Remove the capture filter from the outgoing chain before running the gateway in production. Capturing is typically used only for initial development or debugging and may rapidly fill up your available disk space if left enabled. Substitute the TARGETIP tag with the IP Address of your application. Modify the LoginRequest filter to match the form required for login by your target application.

Proxies all requests and captures them in a flat file. Use this template if you need to analyze the traffic for your application. Simply change the baseURI to be that of the target application, restart the Gateway, and login to the application. The entire sequence will be logged to the flat file. Template

Logs the user into the target application with hard-coded username and password. This template intercepts the login page request and replaces it with the login form. Template

For applications that expect a cookie from the login page to be sent in the login request form. This templates allows the login page request to go through to the target, intercepts the response, then creates the login form and adds the intercepted cookie to the POST. Template

Extracts a hidden value from the login page and includes it in the login form POSTed to the target application. Template

Proxies traffic to an application listening on ports 80 and 443. The assumption is the application uses HTTPS for authentication and HTTP for the general application features. Assuming the login will all take place on port 443, you will need to add the login filters and handlers to the LoginChain. To get started quickly, modify the baseURI to be the IPAddress of your target application. This should allow you to proxy all traffic to the application. Then add the logic for the LoginChain using the flow from one of the login templates. Template

Logs the user into the target application using the headers passed down from an Access Management agent. This template assumes the username and password are passed down by the Access Manager agent as headers. If the header passed in contains only a username or subject and requires a lookup to an external datasource, you will need to add an attribute filter to the chain to retrieve the credentials. Template

A sample template used to log a user into Microsoft Online Outlook Web Access. This template shows how you would use the Gateway and the OpenAM password capture feature to integrate with OWA. Template