AndyHill Posted June 24, 2019 Share Posted June 24, 2019 Our users in AD our made up of a variety of Company names. When importing the users via Azure is there a way to assign them to an organisation based on a particular group membership within the AD rather than by the companyName attribute? The script currently identifies the groups in question in AD "UsersByGroupID":[ { "ObjectID":"Group Object ID", "Name":"Group Object Name" but then assigns them using "Attribute":"{{.companyName}}", "Type":5, "Membership":"member", "TasksView":false, "TasksAction":false Link to comment Share on other sites More sharing options...
SamS Posted June 25, 2019 Share Posted June 25, 2019 Hi @AndyHill, The Attribute... bit allows one to configure the organisational units one can assign the person to (this assumes that the organisational unit (eg Org) is already created in Hornbill). Instead of {{.companyName}} you can use any other Azure attribute. If the value you wish to use as the organisation is already mentioned in one of the attributes, then you can simple substitute .companyName for the name of the Azure attribute. As an alternative, you can hard-code the group name and, with that, just create a new configuration file PER GROUP, so: "UsersByGroupID":[ { "ObjectID":"Group Object ID", "Name":"Specific Group Object Name" } ] would be matched with: { "Attribute":"Specific Group Object Name", "Type":5, "Membership":"member", "TasksView":false, "TasksAction":false } Link to comment Share on other sites More sharing options...
AndyHill Posted June 26, 2019 Author Share Posted June 26, 2019 Hi @SamS. Spot on thanks for this will make importing so much cleaner. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now