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
The wiz_user resource only supports the "Wiz" login type, with no option for SAML integration. The payloads for Update, Read, and Delete are all the same as for the normal user. Where there is a difference is in the Create. A simple extension of the wiz_user to support SAML appears on the surface to have little side effects.
Potential Terraform Configuration
resource"wiz_user""bobsmith" {
assigned_project_ids=["11111-22222-33333-44444-55555"]
email="[email protected]"name="Bob Smith"role="DOCUMENT_READER"idpID="GoogleSSO"# this would match the `wiz_saml_idp.name` fieldsend_email_invite=false
}
wiz_user's have an ID, which looks something like a UUID. When using a SAML provider named (for example) "GoogleSSO" the ID will be googlesso_<UUID>. It is this behavior that allows all subsequent Read, Update, and Delete operations to be performed on the same base "User" type.
Community Note
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
The text was updated successfully, but these errors were encountered:
Description
The
wiz_user
resource only supports the "Wiz" login type, with no option for SAML integration. The payloads for Update, Read, and Delete are all the same as for the normal user. Where there is a difference is in the Create. A simple extension of thewiz_user
to support SAML appears on the surface to have little side effects.Potential Terraform Configuration
References
From the Wiz API Console
wiz_user
's have an ID, which looks something like a UUID. When using a SAML provider named (for example) "GoogleSSO" the ID will begooglesso_<UUID>
. It is this behavior that allows all subsequent Read, Update, and Delete operations to be performed on the same base "User" type.Community Note
The text was updated successfully, but these errors were encountered: