HTTP Federation Proxy Planning Worksheet HTTP Federation Proxy Planning Worksheet
Use this worksheet to record the information you need to configure a connection to an application using HTTP Federation (HFED) Proxy.
| Information | Example | Your Application |
|---|---|---|
| Application basics: | ||
| Application name | Appname Financials | |
| Application sign-in URL | https://www.appname.com/Login.aspx | |
| Application home page URL | https://www.appname.com/welcome | |
| Failure indicators: | ||
| Failure indicator - visible text | Begins with[Invalid credentials] | |
| Failure indicator - URL | Contains[Failed] | |
| Failure indicator - HTTP Status | Matches [401 Unautorized] | |
| Portal hostname and domain name: | ||
| Portal hostname, or identity router virtual IP (VIP) | portal.sso.example.com | |
| Portal protected domain name (PDN) | sso.example.com | |
| Web servers:
Each real application hostname must have a corresponding proxy hostname that is a protected application hostname. Proxy hostnames must be entered as Domain Name System (DNS) canonical names (CNAMEs) to the identity router hostname/virtual IP address. |
||
| Real hostname1 | www.appname.com | |
| Proxy hostname1 | www-appname-com.sso.example.com | |
| Real hostname2 | resources.appname.com | |
| Proxy hostname2 | resources.sso.example.com | |
| Real hostname3 | ||
| Proxy hostname3 | ||
| Real hostname4 | ||
| Proxy hostname4 | ||
| Portal URL: | ||
| Application landing URL (The proxy hostname replaces the real application hostname) | https://www-appname-com.sso.example.com/welcome | |
Related Concepts
Choosing a Connection Method to Add an SSO Agent Application
HTTP Federation Proxy Applications
Related Tasks
Add an Application Using HTTP Federation Proxy
Related References
