Feature/auth docker setup docs

[mahesh-wor]

Description

Please check if the PR fulfills these requirements

• The commit message follows our guidelines: https://github.com/geosolutions-it/MapStore2/blob/master/CONTRIBUTING.md
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (check one with "x", remove the others)

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Docs/Setup Guide
• Other... Please describe:

Issue

What is the current behavior?
Currently we only have setup instructions and docker compose for mapstore/postgres/proxy services.

https://github.com/geosolutions-it/DevOps/issues/1878

What is the new behavior?
This PR introduces optional docker/docker-compose.auth.yml that dev's and users can leverage to have working authentication integration for LDAP/Keycloak. Also includes sample environments and configurations.

Breaking change

Does this PR introduce a breaking change? (check one with "x", remove the other)

• Yes, and I documented them in migration notes
• No

Other useful information

[mahesh-wor]

hi @offtherailz i have fixed the lint issue, along with some docs and sample conf updates. It's ready to review now.

[offtherailz]

See comments inline, there are some issues.

I see a sparse management of LDAP with 3 different implementation and a default in default override --> this is a problem, remove from it

Instead we should use only one LDAP image, properly active and maintained, with only one setup.

Of couse these changes have to be properly reflected in documentation produced for configuration

I can suggest to:

• remove acme-ldap DockerFile
• remove ldif/02-users.ldpf on gitignore and commit it directly, removing ldif.sample
• replace osixia with bitnami/openldap, activiely maintained
• remove changes on docker-compose-override , use a separate override / profile for that
• update web/src/main/resources/ldap.properties from port 10389 a 389 (standard)

[offtherailz]

osixia/openldap is unmaintained

Alternatives:

• bitnami/openldap similar API
• gh.io/nitnelave/lldap light, web UI

We are using 3 different LDAP alternatives...

• acme
• osixia/openldap
• geosolutions-it/openldap

I'd suggest to use only one implemntation, probably based to a maintained one.

[mahesh-wor]

bitnami/openldap is private only, there seems an option to use bitnamilegacy/openldap but it's again legacy and no better than osixia/openldap. osixia/openldap does have v2 but it's in beta.

Writing a custom Dockerfile and init script for building image from scratch might be too much here. Maybe a seperate geosolutions-it/openldap would be nice, if we plan to use dockerized ldap setups.

For now i kept is the same.

[offtherailz]

Please @mahesh-wor look at my comments

[mahesh-wor]

Thank you @offtherailz i will check it and update you.

[mahesh-wor]

hi @offtherailz i have updates to the PR, could you check.

[offtherailz]

the command as written won't start the stack: with --profile test alone compose only enables sut (postgres/mapstore/ldap are all in the base profile), so dockerize times out. It needs --profile base --profile test (verified with docker compose ... config --services). Please double-check the actual invocation you use and document it (e.g. a short note in tests/ or the docs page), since nothing in the repo currently records how to run this stack.
Without documenting it, nobody know what it is needed to and how to run it

So summarizing:

• double check the command correctness
• document docker-compose-test.yml and how to use it, with profile etc...

[mahesh-wor]

hi @offtherailz
i have added documentation regarding use of docker compose test stack. I have added it alongside Unit tests / Lint information in a new sub heading.

https://mapstore--12459.org.readthedocs.build/en/12459/developer-guide/developing/#docker-based-integration-tests

Tests can be achieved with the following, requires two step build. 1st brings base stack up, 2nd runs test containers.

docker compose --profile base -f docker-compose.yml -f docker-compose-override.yml -f tests/docker-compose-tests.yml up -d --build
docker compose --profile test -f docker-compose.yml -f docker-compose-override.yml -f tests/docker-compose-tests.yml up --build --exit-code-from sut

[offtherailz]

Successfully created backport PR for 2026.02.xx:

• [Backport 2026.02.xx] Feature/auth docker setup docs #12694