Page Comparison

...

• Open the Internet Information Services (ISS) Manager
• Create a self-signed certificate
• Add a website
• Add a server farm
• Verify the Routing rule and URL Rewrite Rule
• Configure the Server Affinity
• Configure the Proxy settings
• Configure the load balancer
  
  
  

1. Open the Internet Information Services (ISS) Manager:
   
   1. Windows button → Type and click Server Manager.
      
   2. Under the Servers field, highlight the IIS on the left.
   3. Right click the Proxy Server name.
   4. Select Internet Information Services (IIS) Manager.
2. Create a self-signed certificate:
   1. Go to IIS Manager
   2. Under the Connections field, left-click the server name
   3. Double-click the Server Certificates icon.

   Info

   HTTPS connections require a web certificate. Either self-signed or trusted certificate can be used. In this example, a self-signed certificate is used. You can also use for testing the self-signed certificate created during SSO installation process by importing C:\Program Files\Ubisecure\ubilogin-sso\ubilogin\custom\tomcat\keystore.pfx. This certificate has as alternative subjects both SSO and Accounting Service host names.

3. Click the Self-Signed Certificate under the Actions field.
   1. Assign a name for the certificate.
   2. Use value Personal for the certificate store.

4. Under the Connections field, right-click the Sites → Select Add Website...
   

5. In the Add Website dialog, define the following parameters:

   1. Site name: <your site name>

   2. Physical Path: C:\inetpub\wwwroot

   3. Type: https

   4. Host name: <uas.url from win32.config>

   5. SSL certificate: <certificate created before>
6. Click the OK button.
7. Under the Connections field, right-click the Server Farm.
   1. Select Create Server Farm...

8. Assign a name for the server farm

   1. Click the Next button

9. Add the SSO servers to the server farm.

   1. Define the Server address (host name or IP address).

   2. Under the advanced settings, verify that you have the correct HTTP and HTTPS port numbers. In this example, the default HTTP port 80 is changed to 8080 (from proxy.local.url in win32.config).

   3. Click the Finish button.

10. Click Yes to create a URL rewrite rule to automatically route all incoming requests to your server farm.
11. Under the Connections field, select your Server Farm name
    1. Double-click the Routing Rules icon.
12. Verify that the Use URL Rewrite to inspect incoming requests checkbox is enabled.

13. Under the Actions field, click the URL Rewrite... link.

14. The URL Rewrite name has to use the syntax: ARR_< Server Farm Name >_loadbalance.

    Note
    If you rename the rule it will break the link between ARR (Application Request Routing) and URL Rewrite rule.

15. To open the rule: Right-click the rule name → Select Inbound Rules → Select Edit...

16. Verify the following values:

    1. Action type: Route to Server Farm

    2. Scheme: http://

    3. Server Farm: <Your Server Farm Name>

    4. Path: /{R:0}

17. Click the Conditions drop-down list → Click the Add... button and specify the following values:

    1. Input: {HTTP_HOST}

    2. Check if input string: Matches the Pattern

    3. Pattern: <uas.url from win32.config>

18. Under the Connections field, select your Server Farm name → Double-click the Server Affinity icon.

19. Check the Client affinity checkbox.

20. Under the Actions field, click the Apply.

    Info
    "Sticky Sessions and client affinity are ways of maintaining a persistent connection to a specific webfarm node until the client session ends. When a client connects to a website, the load balancer starts a session on a specific node:  as long as the client is connected, all requests are sent back to that node."

21. Under the Connections field, Select your Server Farm name → Double-click the Proxy icon.

22. Check the Reverse rewrite host in response header checkbox and uncheck the Include TCP port from client IP checkbox.
23. Under the Actions field, click Apply.

24. Under the Connections field, select your Server Farm name → Double-click the Load Balance icon.

25. Under the Load Balance field, configure the parameters:

    1. Load balance algorithm: Weighted round robin

    2. Load distribution: Custom distribution

    3. Relative Weight of SSO Server 1: 1000000000

    4. Relative Weight of SSO Server 2: 1

26. Click Apply under Actions.

    Info
    For High-Performance setup, only proxy related setting is "Load Balance". In High-Performance setup, requests are distributed equally. For High-Performance setup, SSO has to be setup for REDIS in-memory database for session management.

...