Configuration Requirements

• Each resource should be configured using only one of the access methods. Do not mix translated, custom port mapped and custom FQDN-mapped modes.

• Do not include a path in the URL. For example, do not use a URL like:

  http(s)://backend_hostname(:portNumber)

  To set the complete path on WorkPlace, specify the start page on the Edit WorkPlace ShortCuts > Advanced page, as explained in Adding Web Shortcuts.

• Use of valid Certificates is highly recommended.

  • Single sign-on for the appliance might not work with Internet Explorer when a custom FQDN mapped resource with an invalid certificate is accessed from WorkPlace. For example, this could happen when a user logs in to WorkPlace and clicks a custom FQDN mapped resource that has a self-signed certificate or otherwise does not have a valid certificate on the appliance. A JavaScript certificate warning is popped up to the Internet Explorer user. After the user accepts the certificate, Internet Explorer does not transmit the “referrer” HTTP header to the initial page. This referrer value is required for single sign-on functionality. This issue does not occur when using browsers other than Internet Explorer, or when there is no certificate warning, or when wildcard or SAN certificates are used.
  • Custom Port Mapped resource may get redirected to Workplace Portal in case of certificate warning while accessing with Internet Explorer.

• The resources should be configured and accessed using host and domain name only, not via IP address.