Closed fatbasstard closed 1 year ago
Thanks @fatbasstard , @duytiennguyen-okta says he is familiar with what is causing this bug.
Okta internal reference: https://oktainc.atlassian.net/browse/OKTA-611103
I have the same problem using a script that works with previous versions. I went back to 3.46.0 and it works fine.
I have same issue by upgrading to okta tf provider v4.0.0. Apparently, okta_app_oauth from tf provider v4.0.0 would not work with Okta Classic Org (we are still with Classic :-( ). Not sure if Okta would fix it or call it out in the tf documentation. I had to rollback to tf provider v3.46.0 and it worked.
Community Note
Terraform Version
Affected Resource(s)
Terraform Configuration Files
Bit dynamic (handled by a custom module): https://github.com/schubergphilis/terraform-aws-mcaf-cloudfront/blob/master/auth.tf#L53
Debug Output
https://gist.github.com/fatbasstard/37aabf8a6c983a1af0207d3febdb1262
Panic Output
Expected Behavior
Can this be done in the Admin UI?
NO
Can this be done in the actual API call?
I don't know
Actual Behavior
Error: failed to set authentication policy for an OAuth application: error finding default ACCESS_POLICY the API returned an error: The request was not valid: Invalid policy type specified.
Steps to Reproduce
Create new app
terraform apply
Important Factoids
References