Click here to sign up for our mailing list
Hello and welcome to this HelloID Provisioning product release video for January 2020.
HelloID Provisioning is an 100% born in the cloud, easy the configure and to maintain user provisioning solution. It helps organisations to fully automate the user life cycle management in the network by connecting the HR or SIS as a source system. Every change in this source is detected and processed into the network. No worries anymore about stale user accounts, accumulation of licences or access rights, manual user management or compliancy issues.
In this video I first I’d like to start with a PowerPoint presentation and then demo you the new functionalities.
So we have three new options:
The first option is that we improved the exchange performance for the creation and managing performance of mailboxes.
The second option is that we included that you can set the manager in your target system, so if you create a user you can set the managedby attribute for that employee with username of the manager.
The third option, and that’s the most powerful one, now you have a generic connector based on PowerShell to connect any source system to the HelloID vault, so basically you can do connect with any source, like CSV files, Database, Web API. It doesn’t matter, as long as it’s being supported by PowerShell and you can import it into the HelloID vault and then you can propagate that to any connected HelloID target system.
Managedby attribute in the Active Directory
The first item I’d like to show you is how you can manage the managedby attribute in the Active Directory, or in any other target system but I will show it you the active directory on premise situation.
So if I go to the HR system, I’ll look up tjeerds and I will change his contract, Tjeerds is now managed by Bartec and I will change it to Amir. This HR change needs to be propagated into the Active Directory for the user Tjeerds. His managedby attribute must be updated to from Bartec to Amir.
You can save, and now I’ll re-import in helloID. Waiting until it’s re-imported. Go to the user ‘Tjeerd’ and now you’ll see that Amir is the manager and I can also see that the manager attribute for Tjeerd has been updated. I can also show it in the active directory, if I search for Amir, that’s the manager of Tjeerd, now you can see that Tjeerd is also in scope of Amir.
Improved the exchange performance
Another item that we have included is that we can now easily update any active directory user attribute, for example department and company is now not being filled and I can easily update this from HelloID. Go to the target system and you have this, this is a new option.
So let me set the mapping for department and give company the fixed value Enyoi. I save the mapping, and now I do Force Update and now all the attributes will be synchronized from HelloID to, in this case, the active directory. So the Tjeerd Seinen account has been updated so if I go to the system and look up the person again, now you can see that the attributes have been filled in, synchronized from HelloID straight to the active directory.
New source connector
The last item, and this is the biggest item for this release, is the new source connector. This is the PowerShell source connector. So let me delete this source HR system. Now I can add these new systems, these were already available but this is the new one: PowerShell source connector.
This connector is on premise, so it’s running as an agent in your network. You can retrieve data from anywhere as long as it’s PowerShell supported. It can be in a local set of CSV-files, stored in a SQL database, or in a cloud application via the Web API. It doesn’t matter where the data resides, as long as the agent can access the data via PowerShell commands.
So let me show you how you can configure this, I’m not going to change any settings and just click next, next, next. This is the configuration and if I say ‘Okay I just want to run this import’, you can see there is only one demo person. Let me show you where this demo person is defined. This is the powershell script that defines the demo-user, this one is really straightforward, there is no CSV input or whatever, just a simple inline powershell code to set one demo person record.
Let me change this so you can see the immediate effect. So I’m going to change this to myself, display name: Tjeerd Seinen and the first name and last name.
So you save, import in again and now you see it is updated to Tjeerd Seinen, because I changed that in the definition of the PowerShell script, so there it is. If you like you can change the definition to import thousands of users from a CSV file, by just changing that piece of Powershell script.
You can also make other modifications, like the mapping of the data, now these 2 fields are mapped to the displayname. Let me correct this to first name and last name. To do this I need to extend the definition of the connector. You can see I have 2 fields, External ID and Displayname. So I have to extend this with firstname and lastname.
So now I have ExternalID, Displayname, Firstname, and Lastname, we can save it and I can go here to Person, the mapping, and now I have the other options like FirstName and LastName as well, and if I go to my example user you can actually see that the data is being presented.
Okay, for now. Of course the PowerShell source connector is a lot more sophisticated and there will be extensive documentation and training available on how you can use this yourself, so this is just an overview of the functionality and of course there is a lot more to it.
This is the end of this video. Thank you for your time and attention.
Please let us know if you have any additional questions. You can post your question in youtube or send it to email@example.com. Please subscribe to our channel to receive frequent updates about improvements and changes in HelloID.
For now have a wonderful day.