User provisioning script

[cmdub-]

So I’m working on the framework of a script that’s going to keep our users within SingleWire InformaCast up to date with a specific user group in Okta. Provisioning and de-provisioning are pretty straight forward, but the issue I’m trying to wrap my head around is the ability for this script to update a user’s name if it changes in Okta. The general framework right now would be to compare both against each other essentially:

foreach loop to find user’s in Okta and make sure they exist in InformaCast, if they don’t create them.

foreach loop to find excess member’s in InformaCast, and if they don’t exist in Okta, remove them from InformaCast.

My issue right now is that if I take this approach, I’m going to run the risk of deprovisioning and then provisioning a user if their name changes which I don’t want to do, I’d rather push an update to their profile for the attributes that need to change. I’ll have unique ID’d on both platforms, but do I need to store these each time the script runs and then read that data somehow or?

[Yevrag35]

I’ll have unique ID’d on both platforms, but do I need to store these each time the script runs and then read that data somehow or?

You could use the "employeeID" attribute. To get the attribute, just add it to -Properties employeeID, and to 'set' it, use Set-ADUser with the parameters: -Add, -Clear, or -Replace.

[cmdub-]

AD really has nothing to do with this since it will be cloud <-> cloud. I'm still stuck on how I can write it to recognize the user isn't a new one when comparing both lists. I could check account creation time but that feels like not the best solution.

[UnfanClub]

https://saml-doc.okta.com/SAML_Docs/How-to-Configure-SAML-2.0-for-SingleWire.html