Skip to content

updates the documentation for app_signon_policy_rule and list of acceptable value for config office365_client_include #2916

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.

Sign up for GitHub

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

Merged
dhiwakar-okta merged 1 commit into from
Aug 5, 2026
+3 −2
Merged

updates the documentation for app_signon_policy_rule and list of acceptable value for config office365_client_include #2916

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/resources/app_signon_policy_rule.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -370,6 +370,7 @@ resource "okta_app_signon_policy_rule" "test" {
- `users_excluded` (Set of String) Set of User IDs to exclude
- `users_included` (Set of String) Set of User IDs to include
- `chains` (Block List) Authentication method chains. Only supports 5 items in the array. Each chain can support maximum 3 steps. To be used only with verification method type `AUTH_METHOD_CHAIN`.(see [below for nested schema](#nestedblock--chains))
- `office365_client_include` (Set of String) Set of Office 365 Client IDs to include. Only available with Office 365 applications. Valid values include `WEB`, `MODERN_AUTH`, `ACTIVE_SYNC`, `AAD_JOIN`, `CERT_BASED_AUTH`.

### Read-Only

Expand Down
4 changes: 2 additions & 2 deletions okta/services/idaas/resource_okta_app_signon_policy_rule.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -264,10 +264,10 @@ The only difference is that these fields are immutable and can not be managed: '
"office365_client_include": {
Type: schema.TypeSet,
Optional: true,
Description: "Office 365 client types to include. Valid values: WEB, MODERN_AUTH, EXCHANGE_ACTIVE_SYNC, AAD_JOIN. This condition is specific to Office 365 applications.",
Description: "Office 365 client types to include. Valid values: WEB, MODERN_AUTH, ACTIVE_SYNC, AAD_JOIN, CERT_BASED_AUTH. This condition is specific to Office 365 applications.",
Elem: &schema.Schema{
Type: schema.TypeString,
ValidateDiagFunc: validation.ToDiagFunc(validation.StringInSlice([]string{"WEB", "MODERN_AUTH", "EXCHANGE_ACTIVE_SYNC", "AAD_JOIN"}, false)),
ValidateDiagFunc: validation.ToDiagFunc(validation.StringInSlice([]string{"WEB", "MODERN_AUTH", "ACTIVE_SYNC", "AAD_JOIN", "CERT_BASED_AUTH"}, false)),
},
},
},
Expand Down