Scope and Purpose of this Document

This document is created to outline possible ways of integrating the iLobby Address Book with various available Enterprise systems for the purpose of automation of data entry and maintenance.  The goal is to keep the iLobby Address Book updated with latest employee data via sync with another business system.  The approach must be secure, efficient and maintain the desired level of compliance and confidentiality. 

Security and Confidentiality of Data

This document falls under iLobby’s privacy and security policies which mandate sufficient level of encryption and data segmentation to be present throughout the platform.  For the purpose of this document following guidelines are to be followed:

1. Minimum of TLS 1.2 encryption to be used for all data transfers
   
2. All data submissions must be uniquely tokenized or identified using a unique key ID and secret, issued to a specific client.  Client may have more than one key, but each key can only be assigned to one client.
   
3. Expired key/tokens are not to be re-used
   
4. All data must travel from the customer system, directly into protected area of iLobby.  No middle servers/repositories are to be used, unless they are in-scope and makeup the iLobby platform.  Under no circumstances will iLobby request the client to post data to an insecure server, even temporarily.
   
5. VPN and IP restricted connections may be used to further safeguard the data

Synchronizing Data

By default, all data pushed through any of the synchronization mechanisms outlined in this document will take precedence and will overwrite data manually entered.  If empty fields are submitted, they will be ignored and they will not overwrite data already stored.  Data is synchronized based on the email address of the address book entry.  Each sync will add new records to the address book and will mark records not present in the sync as “disabled”. 

Integration Option: Azure / Office 365

iLobby supports direct to Azure/Office 365 integration. This integration will expose the entire contents of the AD to iLobby on “read only” basis.

Please see below the example of the updated PowerShell script for .CSV Address Book sync. 

1. SAMPLE POWERSHELL SCRIPT, CHANGE EXTENSION TO .PS1 PRIOR TO EXECUTION#
2.  
3. <# 1. DEFINE SEARCH LOCATIONS #>
4. $OULocation="OU=Users,DC=TOR"                 
5.  
6. <# 2. SET API CREDENTIALS #>
7. $client_id = ''             
8. $client_secret = ''     
9.  
10. <# 3. SET OUTPUT DIRECTORY #>
11. $sourceFilePath = $PSScriptRoot + "\adextract.csv"     
12. 
    
13. <# 4. SET UP USER PROPERTIES TO EXPORT #>
14. $fields = @('mail','DisplayName','telephoneNumber','HomePhone')   
15. 
    
16.  <# ACTIVE DIRECTORY USER EXPORT TO CSV FILE #> 
17. Import-Module ActiveDirectory                                     
18. $Users = Get-ADUser -Filter {Enabled -eq "True"} -SearchBase $OULocation -SearchScope  Subtree -Properties $fields | select $fields
19. $Users | Export-Csv $sourceFilePath -NoTypeInformation -Force
20. 
    
21. <# GET TOKEN #>
22. $headers=@{}
23. $headers.Add("Content-Type", "application/x-www-form-urlencoded")
24. $response = Invoke-WebRequest -Uri 'https://partnerapi.goilobby.com/auth/connect/token' -Method POST -Headers $headers -Body "grant_type=client_credentials&client_id=$($client_id)&client_secret=$($client_secret)"
25. $token = ConvertFrom-Json $response.Content
26. $access_token = $token.access_token
27. 
    
28. <# UPLOAD CSV FILE TO ILOBBY API #>
29. [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.SecurityProtocolType]::Tls12;
30. $urlDest = "https://partnerapi.goilobby.com/addressbook/uploadcsv";
31. $webClient = New-Object System.Net.WebClient;
32. $webClient.Headers.Add("Content-Type", "application/x-www-form-urlencoded")
33. $webClient.Headers.Add("Authorization", "Bearer $($access_token)");
34. $resp = $webClient.UploadFile($urlDest, "POST", $sourceFilePath); 
35. $enc = [System.Text.Encoding]::ASCII
36. $enc.GetString($resp)

Sample CSV file format

FIRSTNAME,LASTNAME,TITLE,DIVISION,EMAIL,MOBILE,DESKPHONE,SITE

Rob,Jones,Manager,Management,rob.jones@test.com,4169998888,4169997777,Toronto

Sample Office 365 Integration Screens

When requested, iLobby support will provide the client with a unique integration link for establishing the connection between client’s O365 installation and iLobby.  After navigating to the link, client will be presented with the following screens:

Account Selection

This screen will allow the client to select the user account with which the integration link will be established:

Permissions Screen

Once account is selected, iLobby will need to be authorized and granted the permissions required to access the contents of customer’s Office 365 installation:

Application List

iLobby can now be managed in the list of installed applications and services under Enterprise Applications list within the Management tab of your Office 365 management portal: