baton-ipa is a connector for IPA (Identity, Policy & Audit) Servers built using the Baton SDK. It communicates using the LDAP protocol to sync data about roles, users, and groups.
Check out Baton to learn more about the project in general.
To access the IPA server, you must provide the username and password you use to login to the IPA server.
Also see Set up an LDAP connector in the ConductorOne documentation for instructions including using LDAP from ConductorOne.
The latest release is available from the baton-ipa Github releases page.
Pre-built container images compatible with Docker and other container runtimes are published to GHCR:
docker pull ghcr.io/conductorone/baton-ipa:latest
Additionally for testing on workstations, baton-ipa can be installed from Homebrew:
brew install conductorone/baton/baton conductorone/baton/baton-ipa
| CLI Flag | Environment Variable | Explaination |
|---|---|---|
--bind-dn |
BATON_BIND_DN |
required Username to bind to the LDAP server with, for example: cn=baton-service-account,ou=users,dc=baton,dc=example,dc=com |
--password |
BATON_PASSWORD |
optional Password to bind to the LDAP server with. If unset, an unathenticated bind is attempted. |
--url |
BATON_URL |
required URL to the LDAP server. Can be either ldap: or ldaps: schemes, sets the hostname, and optionally a port number. For example: ldaps://ldap.example.com:636 |
--base-dn |
BATON_BASE_DN |
optional Base Distinguished name to search for LDAP objects in, for example DC=example,DC=com |
--user-search-dn |
BATON_USER_SEARCH_DN |
optional Distinguished name to search for User objects in. If unset the Base DN is used. |
--group-search-dn |
BATON_GROUP_SEARCH_DN |
optional Distinguished name to search for User objects in. If unset the Base DN is used. |
--provisioning |
BATON_PROVISIONING |
optional Enable Provisioning of Groups and Roles by baton-ipa. true or false. Defaults to false |
Use baton-ipa --help to see all configuration flags and environment variables.
brew install podman
podman machine init
podman machine start
Warning: Proceed with caution. By default, rootless users are not allowed to bind to ports under 1024. FreeIPA requires ports 80 and 443 for access to the admin UI. If you are only accessing via LDAP, skip this step.
podman machine ssh
sudo vi /etc/sysctl.conf
### Add the following entry to /etc/sysctl.conf:
net.ipv4.ip_unprivileged_port_start=80
### Save and exit session
podman machine stop
podman machine start
podman pull quay.io/freeipa/freeipa-server:almalinux-10
podman volume create freeipa-data
podman run --name freeipa -ti -h ipa.example.test --read-only \
-v freeipa-data:/data:Z \
-e PASSWORD=Secret123 \
-p 80:80 -p 22389:389 -p 22636:636 -p 443:443 \
freeipa-server:almalinux-10 ipa-server-install -r EXAMPLE.TEST --no-ntp --no-ui-redirect
# You will be prompted with a series of configuration questions. Fill them out to complete the configuration.
The FreeIPA container requires access via a domain name.
Configure a hosts entry on your local machine to point example.test to 127.0.0.1.
Edit /etc/hosts and add an entry:
ipa.example.test 127.0.0.1
The Admin UI should accessible by browsing to https://ipa.example.test.
Username: admin
Password: Secret123
FreeIPA should now be running. Create new resources on the FreeIPA server. Use the baton-ipa cli to sync the data from the FreeIPA server with the example command below.
baton-ipa --url ldap://localhost:22389 --bind-dn uid=admin,cn=users,cn=accounts,dc=example,dc=test --password Secret123
After successfully syncing data, use the baton CLI to list the resources and see the synced data.
baton resources
baton stats
baton-ipa will fetch information about the following IPA resources:
- Users
- Roles
- Groups
- Host
- Host Groups
- HBAC Rules
baton-ipa will sync information only from under the base DN specified by the --base-dn flag in the configuration.
We started Baton because we were tired of taking screenshots and manually building spreadsheets. We welcome contributions, and ideas, no matter how small -- our goal is to make identity and permissions sprawl less painful for everyone. If you have questions, problems, or ideas: Please open a Github Issue!
See CONTRIBUTING.md for more details.
