Describe the bug
Actions within the rules JSON blob in the okta_authentication_policy are not populated. They are, however, returned in the underlying API requests (i.e., the data is available). This means its not possible to determine sign on policy settings, for example whether a managed device or phish resistant factor is required; this data would be very useful for determining whether an application is compliant with company policies.
Steampipe version (steampipe -v)
v0.23.2
Plugin version (steampipe plugin list)
v0.12.1
To reproduce
Run select rules from okta.okta_authentication_policy. Note actions in JSON blob is always empty. Examine the underlying API calls to observe that the value of the actions key is not, in fact, empty.
Describe the bug Actions within the rules JSON blob in the okta_authentication_policy are not populated. They are, however, returned in the underlying API requests (i.e., the data is available). This means its not possible to determine sign on policy settings, for example whether a managed device or phish resistant factor is required; this data would be very useful for determining whether an application is compliant with company policies.
Steampipe version (
steampipe -v) v0.23.2Plugin version (
steampipe plugin list) v0.12.1To reproduce Run
select rules from okta.okta_authentication_policy. Noteactionsin JSON blob is always empty. Examine the underlying API calls to observe that the value of theactionskey is not, in fact, empty.Expected behavior Actions to be populated.
Additional context This Okta SDK issue looks like the root cause: https://github.com/okta/okta-sdk-golang/issues/286.
Potential workaround here: https://github.com/okta/okta-sdk-golang/issues/286#issuecomment-1466061997