Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info

This Guide describes how to set automatic Single Sign-On via Active Directory.

WMS Version: 5.X0 / 4.010X

Created: March 2019

Permalink:  https://confluence.wildix.com/x/rABOAg

Table of Contents

Step 1. Generate KeyTab file in Active Directory

  • Go to Active Directory Users and Computers -> Computers
  • Create a new computer account. Note, that this account should not contain a user with the same name
PDF avoid Pagebreak

  • To create KeyTab file and check spn (service principal name) binding to the computer account, run the following commands with Domain Admin privileges:

    Code Block
    ktpass -princ HTTP/some-name.example.com@EXAMPLE.COM -mapuser some-name$@EXAMPLE.COM -crypto ALL -ptype KRB5_NT_SRV_HST +rndpass -out d:\some-name.keytab
    Reset SOME-NAME$'s password [y/n]? y
    setspn -Q HTTP/some-name.example.com

    where

    some-name$@EXAMPLE.COM - the computer's name in the asset directory (with $)

    + rndpass - the password that is generated for the computer account, where the domain is written in capital letters

    If HTTP / some-name.example.com is bound to several computers or users, authentication of Kerberos will not work

  • When KeyTab is generated, it appears on the disk - d: \ some-name.keytab:
PDF avoid Pagebreak

Step 2. Upload KeyTab file to PBX

  • Go to WMS Settings -> PBX -> Security
  • Check offEnable Active Directory Single SignOn via Kerberos (Negotiate)
  • Upload KeyTab file previously generated in Active Directory 

    Note

    Limitation: Only "0-9", "a-z", "A-Z", "_," '- ", "@", "." characters are allowed in KeyTab file name.


  • Enter Kerberos FQDN of the KeyTab. It contains encoded domain name/ IP address of PBX:
PDF avoid Pagebreak

Image RemovedImage Added

Step 3. Import users from AD

In order to use AD SSO, you need to import users from Active Directory.

Consult Documentation for  for details.

Step 4. Active Directory SSO

  • On Windows PC, connected to Active Directory, log in to the system with a user who was previously imported to PBX
  • Reach PBX via the domain name configured as Kerberos FQDN (the name must be resolved to PBX IP address). For example, glebka-test1.wildix2016.inc  

    Note

    Note: Configure your browser to authenticate SSO. Refer to the next chapter Browser configuration.


  • If everything is set up correctly, then you log in automatically to Collaboration with the user that you are logged in to Windows PC

Browser configuration

Mozilla Firefox

To access Firefox settings, enter enter about:config into  into the Address bar and press [Enter] to open the list of customizable preferences for the current browser's installation.

You need to add FQDN of your PBX into the list of trusted URIs:

  • network.negotiate-auth.trusted-uris - FQDN of the Server

On "Login Page" can you find the right for FQDN.

Chrome

To access Chrome settings:

  • auth-server-whitelist -Allowed FQDN - Set the FQDN of the IdP Server. Example:  

    Code Block
    chrome --auth-server-whitelist="*aai-logon.domain-a.com"


On "Login Page" can you find the right for FQDN.

Opera

Opera does not currently support Kerberos authentication.

HTML
<div class="fb-like" data-href="https://confluence.wildix.com/x/rABOAg" data-layout="button_count" data-action="recommend" data-size="large" data-show-faces="true" data-share="true"></div>

...