How to use the AD connector to link Applications to Users & Devices via an AD group

Modified on Tue, 17 Dec at 5:11 PM

TABLE OF CONTENTS

Introduction

Most Organisations associate AD groups with many applications. An admin can use the groups to assign Users or Devices  access to the application. For example, if an admin wants to assign access for the finance department to use a financial application e.g Reuters Eikon , they can create an AD group that contains the users in the Financial department and then assign that group to the application that is needed by the finance dept. This article outlines the steps required to set this up within ManagementStudio. 


Add the AD groups to the Application

  • Switch to the Applications (1) module.
  • Double click on the required Application (2) on the grid.



  • Click on the Connector (1) tab .
  • Select the AD connector tab (2).
  • Add in the corresponding AD group in the App AD Required Group (3)text block.
  • Click Save Changes (4).



Enable Feature in the AD Connector

  • Switch to Administration.
  • Scroll down and click on Extensions.
  • Click Connectors.
  • Select the AD Connector tab from the left menu.
  • Scroll down to Application Update Option and set this to enable.
  • Select the Options required - Please refer to the table below for more information.
  • Once done, click Save Changes at the top to commit the changes
  • When next the AD connector runs, it will create the link between the Application and the Users or devices.



The table below provides information on the elements within this panel.


UI ElementDescription
Link Users to Apps via AD GroupsLink: Creates a User-App links if the User is in ManagementStudio.
Remove: Takes the App off the User if they removed from the AD Group.
User Name FormatAn option to display the format of the list of Users that are imported from the AD Group.
Link Devices to Apps via AD GroupsLink: Creates a Device-App links if the Device is in ManagementStudio.
Remove: Removes the App of the Device if it is removed from the AD Group.
Device Name FormatThe format of the list of Devices that are imported from the AD group.
Recurse Nested App GroupsSearch down the AD Tree of Sub-Groups for Users/Devices. This can be very slow and AD intensive. It is recommended to only use if necessary.
Import Application OU Path as BlueprintThis option converts a App to Blueprint. For example 'AD Info\User\UK\Front Office'
If App Blueprint is BlankIf Department is blank, then: Skip, or use 'AD Info\Name' or use 'AD Info\,black.\Name'.
Starting App Blueprint Folder PathPrefix the Blueprint in the Mappings table with this root path. For example 'AD Info\'.





Further Support

If you require further support, please visit ManagementStudio's Service Desk to search the knowledge base or create a new support ticket.