terraform-provider-okta
terraform-provider-okta copied to clipboard
Support for setting "risc_level" on "okta_app_signon_policy_rule "resource
Okta added the condition of risk assessment to Okta Identity Engine for the application sign-on rules. Unable to set risk level using the "okta_app_signon_policy_rule "resource.
Community Note
- Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
- Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment
Terraform Version
Terraform v1.0.11
- provider registry.terraform.io/okta/okta v3.20.2
Affected Resource(s)
- okta_app_signon_policy_rule
Expected Behavior
Actual Behavior
│ Error: Unsupported argument
│
│ on test_signon.tf line 18, in resource "okta_app_signon_policy_rule" "proofpoint_signon_rule":
│ 18: risc_level = "ANY"
│
│ An argument named "risc_level" is not expected here.
Hi, @rc-ssoltau! Thanks for submitting this issue! risc_level
field is only present in the okta_policy_rule_signon
resource.
Hello @bogdanprodanj , Thanks for the quick response!
I think I might have placed this request in the wrong place, I was intending to add this as a feature request since setting risk-level on application sign-on rules is now supported in the UI within the new Okta Identity Engine tenants.
Feel free to close this Issue and I can re-create it in the appropriate spot
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 5 days
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 5 days
I'll be addressing this.
@monde if you will address it, then maybe also think about renaming into risK_level
? instead of risc_level
?
and also update documentation related to this.
@DenisBalan the risc/risk naming caught me up the other day as well.
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 5 days