-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to create a okta user with custom user-type #12
Comments
judging by the error it seams that your okta credentials are not properly setup, generally speaking you should have created a ProviderConfig Complete docs apiVersion: okta.upbound.io/v1beta1
kind: ProviderConfig
metadata:
name: okta-provider-config
spec:
credentials:
source: Secret
secretRef:
name: okta-creds # this can be anything
namespace: crossplane-system # this can be anything
key: credentials If you are using a kubernetes secrets to hold your credentials it should be similar to what the terraform provider needs Example usage. Assuming you're using an api token it should be similar to or adjust to whatever your integration is needed: {
"base_url": "okta.com",
"org_name": "<your org name>",
"api_token": "<api_token>"
} |
Thank you for the suggestion, @rjop-hccgt, but I have successfully created other resource types in the correct organization with the current provider configuration. I set the provider's log level to debug and observed the following messages:
|
@ebellani77 I would probably check Okta's log from the admin console, it seems that Okta is rejecting the creation for one reason or another, it seems that the YAML definition is correct and is being sent to okta. |
@rjop-hccgt The issue is probably related to the Okta Terraform provider as described here. To check what is described in the issue I executed the following steps:
2- I modified the type of the user directly on the Okta console;
And the magic happened, the resource before stuck, now results READY: true and SYNCED: true.
As a double-check, I used Okta APIs for each step mentioned above, and below is the result: 1- normal user creation:
2- Okta user type manually modified from
3- I manually edited the cr:
Finally, I checked the Terraform state inside the Crossplane provider pod and it appears as expected.
Now, I have changed my focus to understanding how to fix the Okta terraform provider 🙂 |
As a compendium, I found this issue on Terraform Okta provider repo, clearing any doubts. |
Hi guys,
I try to create a user with a custom user-type using the following cr:
but the resource stuck with READY: Flase and SYNCED: true with the following error message:
Would you happen to have any suggestions?
The text was updated successfully, but these errors were encountered: