terraform-provider-okta: Office 365-specific policy cannot be properly configured

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

Description

Office 365-specific policy rule cannot be properly configured as the office365Client attribute is not available nor retrieved.

New or Affected Resource(s)

okta_app_signon_policy_rule

Potential Terraform Configuration

# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file. For
# security, you can also encrypt the files using our GPG public key.

References

#0000

About this issue

Original URL
State: open
Created 2 years ago
Reactions: 8
Comments: 16 (7 by maintainers)

Most upvoted comments

@eduhamel the Okta API is rolling out EA access for configuring an O365 OIN app (and other OIN apps) via the Okta API in November/December. I believe it will be GA in January. Once that is deployed we’ll be able to generate an okta-sdk-golang that the terraform provider uses to communicate with the API and 100% support the office 365 OIN app in terraform.

cc: @duytiennguyen-okta @jefftaylor-okta

monde on Oct 12, 2023

not stale

Bumping issues to ward off StaleBot should no longer be required If the Stale Label isn’t on the issue, it shouldn’t get closed out See the following PRs for reference 🙂 https://github.com/okta/terraform-provider-okta/pull/1697 https://github.com/okta/terraform-provider-okta/pull/1688

this means that we can now all follow the community notice and keep issue comments clean and on-topic 😃

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

exitcode0 on Sep 7, 2023

This is not related to the office365 issue that occurred last week, I just tested it again.

Le mar. 29 nov. 2022 à 17:22, Mike Mondragon @.***> a écrit :

Also, I’m told last week, from the 15th to the 17th, there was a greater issue with the office365 app across the Okta service, see: https://status.okta.com/#incident/a9C4z000000Yzi5EAC @eduhamel https://github.com/eduhamel can you try running your config again?

— Reply to this email directly, view it on GitHub https://github.com/okta/terraform-provider-okta/issues/1387#issuecomment-1330906591, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATCHKD7TZOJHM63FLRDAVXTWKYUV5ANCNFSM6AAAAAASNCTHRA . You are receiving this because you were mentioned.Message ID: @.***>

–

Etienne Duhamel

Consultant Cybersécurité

https://www.facebook.com/SynetisFR/ https://fr.linkedin.com/company/synetis https://twitter.com/SYNETIS?ref_src=twsrc^google|twcamp^serp|twgr^author

@.***

M : +33 (0)7 64 46 85 78 Tél :+33 1 47 64 48 66

www.synetis.com | 19 rue du Général Foy, 75008 Paris

eduhamel on Nov 29, 2022

I think this one will benefit when we bring better Okta Integration Network app support into the API

Other issues having touches on OIN: https://github.com/okta/terraform-provider-okta/issues/1304 https://github.com/okta/terraform-provider-okta/issues/1342

Okta Internal Reference: https://oktainc.atlassian.net/browse/OKTA-552937

monde on Nov 29, 2022