For the complete documentation index, see llms.txt. This page is also available as Markdown.

OneLogin Roles

OneLogin roles membership facilitates the organization of users into logical units, enabling streamlined management of access permissions and policies.

Example Usage


onelogin-group-integration.tf
resource "apono_integration" "onelogin-group-integration" {
  name                     = "OneLogin Roles"
  type                     = "onelogin-group"
  connector_id             = "apono-connector-id"
  connected_resource_types = ["onelogin-role"]
  metadata = {
    subdomain = "<Subdomain>"
  }
  kubernetes_secret = {
    name      = "name_template_value"
    namespace = "namespace_template_value"
  }
}
onelogin-group-integration.tf
resource "apono_resource_integration" "onelogin-group-integration" {
  name                     = "OneLogin Roles"
  type                     = "onelogin-group"
  connector_id             = "apono-connector-id"
  connected_resource_types = ["onelogin-role"]
  integration_config = {
    subdomain = "<Subdomain>"
  }
  secret_store_config = {
    kubernetes = {
      name      = "name_template_value"
      namespace = "namespace_template_value"
    }
}

Schema


  • type onelogin-group

  • connected_resource_types List of resource types to sync.

Available resource types you can use
  • onelogin-role

Integration Config


  • subdomain (Required | String) Subdomain

Last updated

Was this helpful?