For 20+ years I have used LDAP-based metadirectory tools, across the whole range of vendors, as IAM data and access hubs - they ALL share ONE thing in common --- the ability to perform incremental updates to object attributes via a script. The ability to use ldapsearch on a set of users based on data driven criteria, make a text file of data changes, and then run an ldapmodify to remediate is pervasive, assumed, and core to administrative tasks. It's mind-boggling, inexcusable, and headscratchingly a FAIL by the Okta product team. Oh yea, there's rockstar - great. Nothing that postman can't do. Organizations like mine, and the dozens of others that I have served over the years - as the IAM architecture evolves - so do the data requirements. What is the Okta answer to these questions? The success of an organization committed to using Okta has to deal with the constant flow of evolution of data requirements - one week its adding a status flag for a particular lifecycle event, the next week its adding additional attributes for ABAC-based Okta group assignments, etc. etc. What are we Okta admins supposed to do to manage these constant data requirement changes? Update 2 attributes for 300 users in a morning?

To not be a big negative Nancy about all this - Okta really excels at where its focus is, and as customers it helps greatly. Close the barndoor on this one Okta!