Infinite Recursion on Schema Fetching Step on 389 Directory Service

[araujoarthur]

Describe the bug
Hello! I've been learning about directory servers and installed 389 Directory Server to put it in practice, and decided to add phpLDAPadmin to better visualize and manipulate the directory. I couldn't make it run. I had two collateral issues caused by the actual problem: First I had a memory cap issue on Apache, then I had a timeout from PHP, and after solving that I finally had the stack overflow caused by the infinite recursion when fetching the schema.

I know the directory is at least reachable because CLI tools can access it, so does Apache Directory Studio and Cockpit's manager.

I don't know if it's a bug or I'm missing something during the configuration, but I couldn't find anything on the internet about this problem on PLA so either I searched the wrong way, or it's too stupid do even be asked or it's worth mentioning in the wiki.

Version of PLA
Latest container deployed (71943e7d24e5)

To Reproduce
Steps to reproduce the behavior:

1. Install 389 Directory Service (I tried both via CLI and via Cockpit and got the same result)
2. Initialize it with the Suffix entry
3. Pull and run the container, I used the following string:

docker run -itd -v "/home/myuser/dev/phpLDAPadmin overrides/memory-limit.ini":/usr/local/etc/php/conf.d/memory-limit.ini:ro -v "/home/myuser/dev/phpLDAPadmin overrides/time-limit.ini":/usr/local/etc/php/conf.d/time-limit.ini:ro -e LDAP_ALLOW_GUEST=true -e LDAP_HOST=192.168.1.xxx -e LDAP_BASE_DN="dc=mydomain,dc=com,dc=br" -e LDAP_NAME="mydir" -p 8088:8080 --name pla phpldapadmin/phpldapadmin

Where memory-limit.ini adds the rule memory_limit = 512M and time-limit.ini adds max_execution_time = 120(to solve both the memory cap and the timeout).

4. Access the server (I have it on 8088 because it's behind a reverse proxy so I keep my Apache up on the host, but the issue raises when accessing it through localhost:8088 too)

Expected behavior
The tree page to show or a configuration error in the logs. Right now it seems (to me, php illiterate) that PLA is struggling to parse the attributes it received.

Logs
In this gist you can find all LDAP logs as well as Laravel's log.

Here you can check that:

• The LDAP server is reachable;
• The Bind occurs;
• The connection dies because of a stack limit reach.

LDAP Server details (please complete the following information):

• OS: Fedora Linux 42 Server Edition
• Server Name 389 Directory Service (389-ds-base-3.1.2-4.fc42.x86_64 [389-Directory/3.1.2 B2025.045.0000]
• Version 3.1.2

Additional context
As I said above, I am not sure it's a bug, but the lack of content regarding this made me open the issue. Thanks.

[leenooks]

@araujoarthur 389 directory server is not supported (yet) - PLA v2 hasnt been tested with it. I'll spin up an environment and see what's needed to be done (if anything).

[araujoarthur]

Oh I totally misunderstood it then. I was guiding myself by the readme in Docker Hub that seems not to support checkboxes like git flavoured markdown, and makes it seem like that 389 and AD are indeed supported. After your comment I have read Github's readme and totally got it. I'm sorry for the confusion.

If I can help with anything lmk. I'm probably not useful with actual php code at all, but I could pull some improvement to the docs :)

[leenooks]

OK, it was a quirk of 389 DS - but alas an easy fix when I tracked it down. Please test a 2.1-dev image created after today (on docker hub now) and let me know how your testing goes.

You shouldnt need your memory-limit.ini - my testing shows PLA uses ~30MB of ram, and takes ~1s to render the schema and an entry (with caching disabled).

[araujoarthur]

It definitely correctly fetches the schema now, although it doesn't seem to be 100% (for example, I ran into issues trying to change a password, gonna). I also verified that in some (still unclear which) circumstances after a failed login attempt it fails to load the children of the base DN. Anyways, this issue is clearly resolved. I'll open another when I can affirm it's a software problem and not a me problem, and can correctly outline and reproduce the problems I face.

Thank you :)