sigb.us/ldap-proxy
1
0
Fork 0
Code Issues Pull requests Packages Projects Releases Wiki Activity
Fork of https://github.com/netauth/ldap containing extensions specific to sigb.us services
25 commits 1 branch 0 tags 133 KiB
Go 91.9%
Shell 6.3%
Dockerfile 1.8%
Find a file
Michael Aldridge 0eef9f2b22 Push release to correct repo
2021-03-18 01:27:53 -07:00
.github/workflows Push release to correct repo 2021-03-18 01:27:53 -07:00
internal internal/ldap: Correctly handle multi-valued attributes 2020-11-08 19:33:21 -08:00
scripts Fix NOTICE generation 2021-03-18 01:16:30 -07:00
.gitignore meta: Add release machinery 2020-08-23 22:46:37 -07:00
.goreleaser.yml Push release to correct repo 2021-03-18 01:27:53 -07:00
Dockerfile Shrink docker container 2020-11-10 22:59:53 -08:00
go.mod Update to netauth v0.4.0 2021-03-18 00:37:19 -07:00
go.sum Update to netauth v0.4.0 2021-03-18 00:37:19 -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.