@nate.barbettini We use the ‘legacy’ Python SDK to provision new users from our Google Cloud based application that’s integrated with Okta through OpenID/Connect.
Instead having our support people add people in Okta, we do this through our UI and provision the users in Okta using the Python API, same as triggering an activation email.
We’re about to implement JIT user creation for customers that want to use their own Identity Provider through SAML, and will pull user information out of Okta, again using the Python API to figure out what do on our application end.
So basically our Python API need is to lookup create, update and delete users in Okta. Having a supported API is preferred, but the existing Python okta API has worked for years now without problems so we currently don’t see a need to make changes.
On this legacy note: do you expect Okta to make changes on the Okta side that will break the legacy API in the future? This would be bad, but I guess we’d catch these problems in our sandbox first…