The following table describes the fields available for managing applications on the Sites window.
Field | Required | Description |
---|---|---|
Name |
Yes |
Enter a unique Site Name, up to 64 characters, including special characters and spaces. |
Targets |
Yes |
Specify one or more Targets. The format for
this is |
Secure |
Yes |
Select Secure if the site is expecting HTTPS connections. If the site is configured for Secure connections, select a Trusted Certificate Group from the list, or select Trust Any to trust any certificate presented by the listed targets. |
Site Authenticators |
No |
If the site requires the use of site authenticators, select one or more authenticators from the list. Click + Create to create a site authenticator. Click x to remove a site authenticator. |
Use Target Host Header |
No |
Select the check box to have PingAccess modify the
Note:
When cleared, PingAccess
makes no changes to the |
Skip Hostname Verification |
No |
Select this check box if the site should not perform hostname verification of the certificate. |
Expected Certificate Hostname |
No |
If you have not selected to skip host name verification, enter the name of the host expected in the certificate in the Expected Certificate Hostname field. This field is available only if the Skip Hostname Verification check box is not selected. If left blank, the certificates are verified using the target host names. |
Availability Profile |
No |
Select an Availability profile. To create a new availability profile, click + Create Availability Profile. |
Load Balancing Strategy |
No |
If the site contains more than one target, select a Load balancing strategy. To create a new load balancing strategy, click + Create Load Balancing Strategy. |
Send Token |
No |
If your site uses the identity information in the PingAccess Token or OAuth access token, leave this check box selected to include the token in the request to the backend site. If you do not need the token information, you can clear the check box to remove the PingAccess Token from the request. This excludes unnecessary information and decreases the payload size, which might improve performance. |
Maximum Connections |
Yes |
Enter the maximum number of HTTP persistent connections you want PingAccess to have open and maintain for the site. The default of -1 indicates unlimited connections. |
Maximum Websocket Connections |
Yes |
If the number of WebSocket connections needs to be limited, enter a value. The default of -1 indicates no limit. |
Use Proxy |
No |
Select if requests to the site should use a configured proxy. Note:
If the node is not configured with a proxy, requests are made directly to the site. CAUTION:
If your proxy uses availability handling to retry multiple targets in the event of a network problem, you should configure PingAccess to use only one target for the site. Unexpected behavior can occur if PingAccess and the proxy are both configured to perform availability handling. |
Keep Alive Timeout |
No |
The time, in milliseconds, that a pooled connection to the site can be idle before PingAccess closes the connection and removes it from the pool. The default of 0 indicates no timeout. |