MICROSOFT LYNC LOGOS WINDOWS
Step 4: Add a key to the Windows registry on the Lync server. The value of the contactId parameter is the email address in the URI SIP parameter corresponding to the Lync contact associated with the enabled contextual menu command.In the next step where you add a key to the Windows registry, this will enable a redirection to this page in order to define the following type of URL. In this step, you will define a Back Office Web page using your preferred language (PHP, etc.) to keep the email address only in the URI SIP parameter. Step 3: Create a Back Office PHP Web page. Copy and paste the link in the URL field. In Service Manager, select Administration > Access Management > Auto Connection Link in the menu.Ģ. To find out more, see the auto connection link.ġ. This step consists of converting the ID ( URI SIP parameter) of the Lync contact (associated with the enabled contextual menu command) into a unique ID in your Service Manager environment using the two specific URLs mentioned in step 1. Step 2: Create a Back Office PHP Web page. The profile of Service Desk technicians running the contextual menu command in the Lync conversation window must authorize them to use the Service Manager quick call screen for incidents.The SSO mechanism must be enabled on your SaaS-based Service Manager platform.You must have the relevant rights and privileges for adding a key to the Windows registry on the Microsoft Lync server.Your Active Directory must be correctly synchronized with the SaaS-based Service Manager employee directory.This value will be the unique ID between Microsoft Active Directory and the Lync server and your Service Manager environment ( USERID). based on your configuration) as the value of the url_requestor parameter in the PHP pages indicated below. The important point is to pass the email address of a user identified in your Service Manager employee directory (e.g. Depending on your business requirements, you can use other methods or development languages to produce similar or different results. The other information described in the integration process, such as the registry key and Back Office PHP Web page, should be taken as an illustration and, as it does not come from Service Manager Support, may not correspond to your specific requirements. You should submit your request to the Support team. Step 4: Run the command in the Lync client.įor SaaS-based Service Manager, EasyVista can provide and configure two specific PHP Web pages for SSO authentication to help you integrate Microsoft Lync.Step 3: Add a key to the Windows registry on the Lync server.Step 2: Create a Back Office PHP Web page.Step 1: Check the list of requirements.Using this method, you can integrate Lync in Service Manager in four easy steps: If the email address does not exist, the page will be redirected to the Service Manager login page, sso_samlindex.php.The screen will automatically be pre-loaded with information belonging to the Lync contact. The value of the url_requestor parameter is the email address ( USERID required by Service Manager) of the previously selected Lync contact. If the email address exists, the page is redirected to a specific PHP Web page, sso_samlindexlync.php, that will open the quick call screen in Service Manager (SaaS-based).It checks if the email address in the contactId parameter exists in the Active Directory via the ADUserclass. The Back Office Web page (script) changes the initial parameter value and keeps only the email address (e.g.The URI SIP parameter used is %contact-id% and its value is Contacts=. The command sends a HTTP request to a Back Office PHP Web page by passing the contactId parameter whose value is identical to the URI SIP (or SIP-ID) parameter of the relevant Lync contact.To perform the integration, you add a specific command to a contextual menu in the Lync conversation window by modifying the Windows registry on the Microsoft Lync server.Method 1: Specific Web page, in SaaS version only