Rancher

Create an integration to manage access to a Rancher instance

Rancher is a Kubernetes management platform that simplifies the deployment and management of clusters across any environment, enhancing flexibility, scalability, and resource efficiency.

Through this integration, Apono helps you discover your Kubernetes resources and securely manage access through your Rancher instance.

---

Prerequisites

Item	Description
API Key	Key for authenticating with Rancher comprised of the endpoint, access key, secret, and bearer token Follow these instructions to create an API key: The API key must be created by an admin role user. For the Scope, use No Scope. Limiting the scope will negatively impact the performance of the integration. When choosing the Automatically expire option, be mindful that when the duration has expired a new API key will need to be generated. If a new key is not created, the integration will stop working. After creating the API key, copy the following values to authenticate the Apono integration: Access Key Secret Key
Secret	Value generated through a secret manager Use the following values to generate the secret: "access_key": "RANCHER_ACCESS_KEY", "secret_key": "RANCHER_SECRET_KEY" Apono does not store credentials. The Apono Connector uses the secret to communicate with services in your environment and separates the Apono web app from the environment for maximal security.

---

Integrate Rancher

You can also use the steps below to integrate with Apono using Terraform. In step 10, instead of clicking Confirm, follow the Are you integrating with Apono using Terraform? guidance.

Follow these steps to complete the integration:

1. On the Catalog tab, click Rancher. The Connect Integration page appears.

2. Under Discovery, click Next. The Apono connector section expands.

3. From the dropdown menu, select a connector.

If the desired connector is not listed, click + Add new connector and follow the instructions for creating a connector (AWS, Azure, GCP, Kubernetes).

1. Click Next. The Integration Config section expands.

2. Define the Integration Config settings.

   Setting	Description
   Integration Name	Unique, alphanumeric, user-friendly name used to identify the integration when constructing an access flow
   Host	Hostname of the Rancher server
   Port	Rancher port value
   Certificate Authority (optional)	(Optional) Ensures that the Kubernetes API server you are communicating with is trusted and authentic Leave this field blank to connect the cluster where the Apono connector is deployed.
   Rancher UI URL (optional)	(Optional) URL of your Rancher UI This URL must be reachable from all the hosts that you add.

3. Click Next. The Secret Store section expands.

4. Associate the secret or credentials.

5. Click Next. The Get more with Apono section expands.

6. Define the Get more with Apono settings.

   Setting	Description
   Credential Rotation	(Optional) Number of days after which the database credentials must be rotated Learn more about the Credentials Rotation Policy.
   User cleanup after access is revoked (in days)	(Optional) Defines the number of days after access has been revoked that the user should be deleted Learn more about Periodic User Cleanup & Deletion.
   Custom Access Details	(Optional) Instructions explaining how to access this integration's resources Upon accessing an integration, a message with these instructions will be displayed to end users in the User Portal. The message may include up to 400 characters. To view the message as it appears to end users, click Preview.
   Integration Owner	(Optional) Fallback approver if no resource owner is found Follow these steps to define one or several integration owners: From the Attribute dropdown menu, select User or Group under the relevant identity provider (IdP) platform. From the Value dropdown menu, select one or multiple users or groups. NOTE: When Resource Owner is defined, an Integration Owner must be defined.
   Resource Owner	(Optional) Group or role responsible for managing access approvals or rejections for the resource Follow these steps to define one or several resource owners: Enter a Key name. This value is the name of the tag created in your cloud environment. From the Attribute dropdown menu, select an attribute under the IdP platform to which the key name is associated. Apono will use the value associated with the key (tag) to identify the resource owner. When you update the membership of the group or role in your IdP platform, this change is also reflected in Apono. NOTE: When this setting is defined, an Integration Owner must also be defined.

7. Click Confirm.

💡Are you integrating with Apono using Terraform?

If you want to integrate with Apono using Terraform, follow these steps instead of clicking Confirm:

1. At the top of the screen, click View as Code. A modal appears with the completed Terraform configuration code.

2. Click to copy the code.

3. Make any additional edits.

4. Deploy the code in your Terraform.

Refer to Integration Config Metadata for more details about the schema definition.

Now that you have completed this integration, you can create access flows that grant permission to your Rancher instance.