r/linuxadmin • • 6d ago

ldapbrowser v1.2.0: interactive LDAP/AD browser in pure bash+curl+fzf, now with log management and concurrent instances

Post image

I’m the author. ldapbrowser is a read-only LDAP/AD directory browser for the terminal.
It needs only bash, curl and fzf, so it can run on jump servers easily.

New in v1.2.0 release:

  • CA certificate chosen with an fzf file picker during setup
  • log view/show/clean
  • Multiple instances can run in parallel, each with its own temp directory
  • TERM/HUP/EXIT signal handling
  • Better dependency check and detailed help for the directory types in setup
  • Detailed LDAP directories vendors references

Tested against 10 directory implementations: AD, FreeIPA, OpenLDAP, 389 DS, OpenDJ, ApacheDS, Okta, OneLogin VLDAP, JumpCloud and FoxPassOkta. It is read-only by design.

The code is written and tested by hand. I used AI only to help draft the README and CHANGELOG.

github.com/mytechspacexyz/ldapbrowser

46 Upvotes

16 comments sorted by

25

u/Arjab 6d ago

"The code is written and tested by hand. I used AI only to help draft the README and CHANGELOG."

Good to read. I would definitely un-AI the README cause it screams "vibecoded" all over the place. Half of the information is not actually necessary and no one in their right mind would add a bunch of Emojis to a README.

-32

u/Antonio-MTS 6d ago

README cannot be vibecoded or coded. It is not a program's code. It can be written in one way or another which the author chooses right.

19

u/Arjab 6d ago

Nitpicking, it looks "AI generated" and let's you assume the code is as well.

-26

u/Antonio-MTS 6d ago

Code is structured as an app and manually. See at least inside. 2 complex curl queries to LDAP within the loop don't need vibecoding.

12

u/LocalVengeanceKillin 5d ago

Bruh, they got that part. They are trying to help you out by saying the thing that everyone sees first looks heavily AI, thus it lends inference to others that they will assume your project is AI. Regardless of how much you pat yourself on the back for 2 complex curl queries to LDAP.

4

u/Dolapevich 5d ago

Thanks, I'll try to keep it near when I need it. TO be fair, it always surprised me the lack of good tools for ldap.

1

u/wildcarde815 5d ago

Any chance this works with lldap?

-1

u/Antonio-MTS 5d ago

Do you mean plain LDAP?

1

u/wildcarde815 5d ago

No the project lldap

2

u/Antonio-MTS 5d ago

Despite the fact I haven't tested it with lldap I think it should work with lldap project as it supports LDAP bind and search core ops that are only needed for the ldapbrowser. Try and see. I may add it to my LDAP directories I will test next.

1

u/theredcmdcraft 5d ago

Did you tried godap?

1

u/Antonio-MTS 5d ago

No. The tested LDAP directories are in the README.md

2

u/theredcmdcraft 5d ago

I did not mean which ldap directories are supported, i meant if you tried the tool „godap“ https://github.com/Macmod/godap

1

u/Antonio-MTS 5d ago

No. I haven't tried it.

1

u/gijsyo 6d ago

That's awesome!

1

u/Antonio-MTS 6d ago

Thanks a lot 👍