Views:

Applies To:

GroupID 10 - Self-Service

Business Scenario:

Customers who use Self-Service portal want their end-users to be able to easily access the portal via its URL. To make things easy for their end-users, they generally use HTTP redirection at IIS level on the server or on a load balancer. By doing this, end-users only have to enter the name of the server in the browser to access the portal.

Let's assume that your portal's complete URL is: https://userportal/groupid.

Here, 'userportal' is the hostname of the GroupID server and 'groupid' is the name of the Self-Service portal. After configuring HTTP redirection, end-users will only have to enter 'userportal' in their browsers and they will automatically be redirected to the complete portal URL.

Issue with the above Approach:

By applying redirection in the above example, end-users can access the portal by entering 'userportal' or 'http://userportal'. However, if someone enters 'https://userportal', the portal will not load and give an error message. This is because GroupID creates its own site in IIS which is separate from the Default Website and generally the GroupID site uses port 443 while the Default Website does not have any binding for HTTPS in IIS.

Resolution:

You can resolve this issue by simply placing the attached HTML file named 'Index.html' on your GroupID server at the following path:

X:\Program Files\Imanami\GroupID 10.0\GroupIDSite10\inetpub\wwwroot

The only change that may be required is at line # 6 of the attached file, which reads as:

window.location.href = window.location.href + "/GroupID";

Here, the word 'GroupID' represents a portal's name. If your portal's name is the same, then you do not need to make any change. If your portal has a different name, replace 'GroupID' with that name.

Related Attachments (1)