mirrors/ldap-upstream
1
0
Fork 0
mirror of https://github.com/netauth/ldap.git synced 2024-11-24 04:21:55 -06:00
Code Issues Packages Projects Releases Wiki Activity
Mirror of https://github.com/netauth/ldap
17 commits 1 branch 7 tags 100 KiB
Go 89.5%
Shell 8.1%
Dockerfile 2.4%
Find a file
Michael Aldridge 55b4034696 Add dockerfile
2020-11-09 22:36:02 -08:00
internal internal/ldap: Correctly handle multi-valued attributes 2020-11-08 19:33:21 -08:00
scripts meta: Add release machinery 2020-08-23 22:46:37 -07:00
.gitignore meta: Add release machinery 2020-08-23 22:46:37 -07:00
.goreleaser.yml meta: Add release machinery 2020-08-23 22:46:37 -07:00
Dockerfile Add dockerfile 2020-11-09 22:36:02 -08:00
go.mod internal/ldap: Implement search for entities 2020-08-23 00:17:03 -07:00
go.sum internal/ldap: Handle bind 2020-08-22 20:49:54 -07:00
LICENSE Initial Commit 2020-08-17 01:22:17 -07:00
main.go main: Add defaults 2020-08-23 19:39:32 -07:00
README.md README.md: Update readme 2020-08-23 00:18:54 -07:00

README.md

NetAuth LDAP Server

The NetAuth LDAP server acts as a bridge that allows legacy systems that understand LDAP to gain a read-only view of data in the NetAuth server.

It is recommended to install the NetAuth LDAP server on each host that requires this interface and to bind it to the loopback interface.

The format that the LDAP bridge exposes data in is slightly different to that which is presented to an actual NetAuth client. The groups are presented in a flattened format with all expansions processed, and all groups are precented under a special ou=groups path. Similarly, entities are presented under a ou=entities path under the base DN.

Speaking of the base DN, NetAuth doesn't have such a concept, so the LDAP bridge takes this as a seperate configuration item on startup. The provided format must be a valid domain name that will be split on .. Prepended to this will be dc=netauth to clearly signify that the data retrieved is coming from NetAuth.