Skip to main content
C1 provides identity governance for Apache Ranger. Integrate your Apache Ranger instance with C1 for unified visibility and governance over identities, policies, and access grants managed by Ranger Admin.

Capabilities

The connector reads users, groups, roles, system access roles, admin module permissions, security zones, tags, and policies from the Ranger Admin REST API. Each access policy is synced with one entitlement per access type its allow items grant (for example select or read), plus a delegate-admin entitlement when an allow item delegates admin. Grants resolve the users, groups, and roles referenced in those allow items. Only allow items on access policies are synced. Deny items, allow and deny exceptions, and data mask and row filter policies do not produce entitlements or grants. Two further exclusions apply inside a synced allow item. An access whose isAllowed is explicitly false is skipped, as are principals Ranger resolves at evaluation time rather than storing: the implicit public pseudo-group, and macro tokens such as {OWNER} and {USER}. Entitlements and grants are derived from the same policy rows, so an access type appears as an entitlement only when at least one syncable principal is granted it. Ranger’s default per-service policies commonly grant to public alone; such a policy syncs as a resource with no entitlements and no grants. A disabled policy, one whose isEnabled is false, syncs as a resource with its entitlements but no grants, because Ranger does not enforce it. Users are read from Ranger’s portal user list, which also contains the built-in administrative accounts, such as keyadmin, that the extended user list omits. A user syncs as enabled only when Ranger reports its account status as active. Every other activation status — pending approval, pending activation, rejected, deactivated, pre-registration, and no login — syncs as disabled. This connector supports Apache Ranger 2.x. It is read-only and does not provision or modify access in Apache Ranger. Security zone coverage is reduced before Ranger 2.5. The adminRoles and auditRoles fields were added to the security zone API in Ranger 2.5.0 (RANGER-4274), so on Ranger 2.4 and earlier the role principals on a security zone are not synced. Users and groups on security zones sync normally on every 2.x release. Ranger 2.4 accepts both fields when a zone is created and then silently discards them, so the omission is not reported as an error.

Gather Apache Ranger credentials

You need an Apache Ranger account with administrator access to the Ranger Admin service so the connector can read users, groups, roles, policies, and security zones. An account without admin access may return only a partial view of your directory.The connector authenticates with HTTP basic authentication. Kerberos and SPNEGO authentication to the Ranger Admin REST API are not supported, so a Kerberized cluster needs a Ranger Admin account that accepts basic authentication.
1
Sign in to the Apache Ranger Admin UI. By default it runs on port 6080, for example https://ranger.example.com:6080. Note this base URL — you enter it when configuring the connector.
2
Use an account with administrator access. On a default installation this is the admin user whose password was set during installation. Confirm the account can view Settings > Users/Groups/Roles and policy objects in the Admin UI.
3
Have the username and password for that account ready. The connector authenticates to the Ranger Admin REST API with these credentials.

Configure the Apache Ranger connector

Follow these instructions to use a built-in, no-code connector hosted by C1.
1
In C1, navigate to Apps > Connectors and click Add connector.
2
Search for Apache Ranger and click Add.
3
Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.
4
Set the connector’s Name and, optionally, a Description.
5
Click the pencil icon next to Owners to choose who can configure and manage this connector.
6
Click Add. The connector is created and its configuration page opens.
7
Find the Settings area of the page and click Edit.
8
Enter the Apache Ranger credentials:
  • Base URL: Your Apache Ranger Admin server URL, for example https://ranger.example.com:6080.
  • Username: The administrator username for Ranger Admin.
  • Password: The password for that account.
9
Click Save.
10
The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.
Done. Your Apache Ranger connector is now pulling access data into C1.

Connector configuration reference