LogoLogo
Metadata for Integration Config
Metadata for Integration Config
  • INTEGRATION METADATA
    • Amazon Account
    • AWS EC2 SSH
    • Elastic Kubernetes Service (EKS)
    • AWS Lambda Custom Integration
    • Amazon Organization
    • AWS RDS MySQL
    • AWS RDS PostgreSQL
    • Amazon RDS
    • Entra ID (Azure AD) Groups
    • Azure Kubernetes Service (AKS)
    • Azure Management Group
    • Azure MySQL
    • Azure PostgreSQL
    • Azure Subscription
    • Azure VM SSH
    • Cloud Function Custom Integration
    • F5 Network
    • Google AlloyDB
    • Google Cloud SQL - MySQL
    • Google Cloud SQL - PostgreSQL
    • Google Kubernetes Engine (GKE)
    • Google Organization
    • Google Project
    • Github
    • JumpCloud
    • Kubernetes Proxy
    • Kubernetes
    • LDAP Group
    • MariaDB
    • Mongo Atlas Portal
    • MongoDB Atlas
    • MongoDB
    • Microsoft SQL Server
    • MySQL
    • Okta Group
    • OneLogin Group
    • 1Password
    • OpenSearch
    • OpenVPN
    • Oracle Database
    • PostgreSQL
    • RabbitMQ
    • Rancher
    • RDP
    • Redis Cloud (Redislabs)
    • Amazon Redshift
    • Snowflake
    • SSH
    • Vertica Database
    • Web App
    • Windows Domain Controller
Powered by GitBook
On this page
  • Example Usage
  • Schema
  • Integration Config

Was this helpful?

Export as PDF
  1. INTEGRATION METADATA

OneLogin Group

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 Group"
  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 Group"
  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"
    }
}
onelogin-group-integration.json
{
    "onelogin-group-integration": {
        "name": "OneLogin Group",
        "type": "onelogin-group",
        "connector_id": "apono-connector-id",
        "connected_resource_types": [
            "onelogin-role"
        ],
        "integration_config": {
            "subdomain": "<Subdomain>",
        },
	"secret_store_config": {
    	    "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

PreviousOkta GroupNext1Password

Last updated 1 month ago

Was this helpful?