User model lacks some fields about okta-sdk-python

[joshford05]

Any update on this? We definitely need the ability to update other profile fields within the SDK.

[cobaltjacket]

Hi there. Any update on this? Will we also be able to obtain properties that come into Okta from other directories (i.e. Active Directory)? While we can internally pull these properties from AD as a separate action and perform a join of sorts, it would be nice to run some of these scripts externally, which would mean the information would need to come out of Okta.

One note -- I also use the PowerShell API, and it would be nice to see the same thing there as well.

[dahu33]

Same problem here... Please fix it.

[jmelberg-okta]

Hi @cobaltjacket. We apologize for the long delay.

We are currently in the process of updating this project. This includes the ability to get unmapped properties (e.g. employeeNumber).

Thanks!

[jmelberg-okta]

@cobaltjacket: Thanks for following up!

We are working on providing the best solution for this. This will include storing all fields returned via the Okta API into all of our models. This update, along with a few others will be pushed as a v1.0.0 release to pypi.

Thanks for your patience!

[cobaltjacket]

We're at five months since the last official response. Please advise. Anyone who has commented on this or the similar issues is a paying customer who would like to have this resolved.

[cobaltjacket]

It sounds as if Okta has elected to just abandon this API, rather than keep it up to date.