You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$Activate = $true # Boolean | Executes activation lifecycle operation when creating the user (optional) (default to $true)
$Provider = $true # Boolean | Indicates whether to create a user with a specified authentication provider (optional) (default to $false)
$NextLogin = "changePassword" # UserNextLogin | With activate=true, set nextLogin to ""changePassword"" to have the password be EXPIRED, so user must change it the next time they log in. (optional)
These function names are missing the Okta after the dash
This call is missing the parameter to pass in to VarProfile
there is no value in the key_example
The VarProfile would need an object that contains the username, etc for the new user as a secondary bit once the code is able to run
A quick search of the broader readme's shows these repeated in a few places too
I did look to correct these in a PR, but Im not up to scratch enough on how the management.yaml is created to do this one quickly. If there is any sort of crib sheet on how to tweak these lemme know and I can help with these
The text was updated successfully, but these errors were encountered:
Thank you for reporting this issue and for continuing to help us make this tool better, @TriggerAu!
As you said, we must review the Okta OpenAPI spec and the templates. I filed an internal ticket for the team to review and prioritize in the upcoming planning rounds.
In doing some work on a test framework to read and create Okta user profiles I looked at the read me and found the following issues in the below
okta-powershell-cli/docs/OktaUserApi.md
Lines 286 to 313 in f78b2c6
Annotated some issues I found here:
Okta
after the dashThe VarProfile would need an object that contains the username, etc for the new user as a secondary bit once the code is able to run
A quick search of the broader readme's shows these repeated in a few places too
I did look to correct these in a PR, but Im not up to scratch enough on how the management.yaml is created to do this one quickly. If there is any sort of crib sheet on how to tweak these lemme know and I can help with these
The text was updated successfully, but these errors were encountered: