Skip to content
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.

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

EA Feature - Resource Set Conditions #2133

Open
exitcode0 opened this issue Nov 11, 2024 · 2 comments
Open

EA Feature - Resource Set Conditions #2133

exitcode0 opened this issue Nov 11, 2024 · 2 comments
Labels
enhancement Asking for new behavior or feature triaged Triaged into internal Jira

Comments

@exitcode0
Copy link
Contributor

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

Resource set conditions help you limit the scope of a role by excluding an admin's access to certain apps. This gives you more granular control over your custom admin roles and helps meet your org's unique security needs
https://help.okta.com/oie/en-us/content/topics/security/custom-admin-role/resource-set-conditions.htm

It would be great to add support for this feature to the okta_resource_set resource

New or Affected Resource(s)

  • okta_resource_set

Potential Terraform Configuration

locals {
  org_url = "https://mycompany.okta.com"
}

resource "okta_resource_set" "test" {
  label       = "UsersAppsAndGroups"
  description = "All the users, app and groups"
  resources = [
    format("%s/api/v1/users", local.org_url),
    format("%s/api/v1/apps", local.org_url),
    format("%s/api/v1/groups", local.org_url)
  ]
  conditions {
    exclude = jsonencode({
      "okta:ORN" = [
        "orn:oktapreview:idp:00o3123456789:apps:example:0oa5123456789"
      ]
    }
  }
}

References

  • #0000
@exitcode0 exitcode0 added the enhancement Asking for new behavior or feature label Nov 11, 2024
@duytiennguyen-okta duytiennguyen-okta added the triaged Triaged into internal Jira label Nov 13, 2024
@duytiennguyen-okta
Copy link
Contributor

Is this feature still EA?

@duytiennguyen-okta
Copy link
Contributor

OKTA internal reference https://oktainc.atlassian.net/browse/OKTA-829683

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Asking for new behavior or feature triaged Triaged into internal Jira
Projects
None yet
Development

No branches or pull requests

2 participants