Lucas Cantor

Okta just [published a YouTube video advertising Device Assurance](https://www.youtube.com/watch?v=UERaxr743gk). It looks like a critical capability to have, but we unfortunately still can't use it until this functionality is added. Does...

I strongly agree with this, given Okta's official instruction when enforcing Device Trust is to do exactly this. Currently, we're forced to implement a regular DENY rule at the lowest...

@monde to confirm, is this bug still expected to impact today's new `3.29.0` release?

Looks like this bug is still present in 3.31.0 as well. I'm sorry I don't understand the nature of the root cause to offer a fix ☹️ Is there perhaps...

@tmatilai thanks so much for the advice 🙇🏼

I can confirm adding ``` lifecycle { ignore_changes = [identity_provider] } ``` resolves my issue, allowing me to use `3.31.0`.

Commenting to keep this alive. @monde could the `no-stalebot` label maybe be added so this doesn't get closed? I assume Okta is still committed to supporting Device Assurance.

@pennethus this GitHub issue is for Okta Device Assurance, which doesn't strictly relate to [that risk](https://simplerisk.security.intercom.io/management/view.php?id=1101), which is for Okta Device Trust. However, once this GitHub issue is resolved, we...

This bug still exists. Commenting to prevent auto-closure.

Not stale 🥲