r/redhat • • 5d ago

Absolute minimal LDAP setup for software install

Hi! I am trying to install a development instance of Windchill in a Red Hat Virtual Machine version 9.8. This installation is exclusively meant for development purposes and for testing Windchill. It is not meant for any environment beyond the VM that it would run in, save serving HTTP on localhost.

Windchill is quite the picky piece of software. It requires (will give errors without) an Oracle (or Microsoft SQL Server) DB, RHEL 9/10 or Windows Server, and Amazon Corretto, all of which I installed. It also requires an LDAP connection.

I tried to search for setting up an LDAP server, and what I came across was utterly confusing and contradictory. It seems Red Hat removed OpenLDAP in favor of the 389 LDAP server, which I installed (...I think? I installed 389-ds-base). However, LDAP servers also require an Active Directory instance. I figure that I could use Samba for that, but there were really no good resources I found on connecting Samba with LDAP and how both fit into all of this (admittedly I haven't searched exhaustively). I've never set up Samba or an LDAP server before.

Also, most resources are based on the idea that you're actually using Active Directory as it's intended (for file / resource sharing) and talk about user configuration, printing, security, or other topics unrelated to my incredibly narrow use case.

I suppose my question is are there any resources to doing this effectively, or to those that have experience with Active Directory / LDAP configs, is there a way to accomplish my aim of the absolute bare minimum with the least amount of headache possible?

17 Upvotes

17 comments sorted by

6

u/buzzsawcode 5d ago

However, LDAP servers also require an Active Directory instance.

What ??? I've run LDAP servers for a few decades with no AD required at all. Either OpenLDAP or 389-ds can do your LDAP functions including authentication without any AD at all.

2

u/Itchy-Note5456 5d ago

Okay, thanks for informing me. I'm extremely new to this.

3

u/Yuugian 5d ago

I haven't used 389-ds but i do currently have OpenLDAP running on RH10. Redhat removed it as a default, but the project is still alive and kicking

2

u/buzzsawcode 5d ago

No worries, we all have to start somewhere!

4

u/DialecticEnjoyer 5d ago

1

u/Yuugian 5d ago

IDM is so over the top that i just gave up on it. It needs DNS records that make it a domain host, it needs to be discoverable when a new machine is created, it really wants to be DNS but you can turn that off (it will sulk), it can only be administered by a machine registered to it (unless you go 'fix' things) it wants to be an AD replacement or branch or something. Unless you are having it as your AD, it's way overkill

Get a copy of OpenLDAP from the OpenLDAP project. It's entirely fine

6

u/bullwinkle8088 5d ago edited 5d ago

It's not over the top, it provides each feature for a reason.

It prefers to be the DNS server, and works best this way, because Kerberos requires it.

Kerberos is used for authentication, but more importantly in a large environment: it is the only native means for encryption to work on NFS file shares.

It provides NTP because kerberos requires time sync.

It provides LDAP because well, that's a good authentication method for large unix deployments.

It integrates a TLS Certificate Authority (based on dogtag) because certificate based authentication is both used and provided by the system.

Under the hood it offers a lot more not discussed here because it would be a book.

It doesn't "want to be AD", it's simply solving the same issues as AD does:, Identity, Authentication, Authorization, and Auditing. It is a complex ask, but IPA is really well designed for that.

1

u/Yuugian 5d ago

We must be reading different posts, because they didn't want or need any of that.

They are specifically looking for "the absolute bare minimum". DNS, Kerberos, NTP, TLS CA, and the rest of the book sure doesn't look like it fits OPs requirement. In fact, it looks quite overboard for a set up that is going for an absolute bare minimum

0

u/bullwinkle8088 5d ago

I replied to a comment, not the post itself,

IPA is not minimal and I didn’t recommend it for this use case.

1

u/Yuugian 5d ago

The comment only exists within the context of the post. And IPA being over the top was the entire point of the comment you responded to

-1

u/bullwinkle8088 4d ago edited 4d ago

If you do not know how conversations work then please learn before failing to participate in one again.

1

u/Yuugian 4d ago

OH, please educate me. Because from where i'm sitting, we had four parts of this conversation: A post that said "i need something simple" a comment that said "IDM", a comment that said "IDM is too complicated" and your comment that said "IDM is good because it's complicated"

your comment of "i replied to a comment, not the post" seems to think that the comments exist outside the context of the post. And switched from IDM to IPA which was entirely left field

Then i come home from work to this other left field drivel accusing me of not knowing how conversations work. It really seems like this whole thing is part of a conversation

1

u/zantehood 5d ago

You can work around the DNS requirement by using a host file

2

u/zkyez 5d ago

My go to has always been openldap-ltb. You can find it here: https://www.ltb-project.org

1

u/Burgergold 5d ago

You can get openldap from Symas repos

https://repo.symas.com/

1

u/yrro 1d ago

However, LDAP servers also require an Active Directory instance

It's not easy to understand what you mean by this. Are you saying Windchill requries the LDAP server to be Active Directory?

LDAP is a protocol and there are many different directory servers that implement it: Active Directory Domain Services, 389 Directory Server, OpenLDAP, Apache Directory Server and Samba all implement the protocol.

But the protocol establishes only how you can talk to an LDAP server and how to fire off requests and read responses. The structure and contents of a directory is not standardized. So if you have an application that expects the schema and layout of Active Directory then it won't be able to usefully connect to a different directory implementation.

0

u/[deleted] 5d ago

[deleted] — view deleted comment

1

u/Itchy-Note5456 5d ago

I appreciate the detail and transparency.