georchestra/security-proxy repository overview

⁠Quick reference

• Maintained by:
  georchestra.org⁠

• Where to get help:
  the geOrchestra Github repo⁠, IRC chat⁠, Stack Overflow

⁠Featured tags

• latest, 25.0.x, 24.0.x

⁠Quick reference

• Where to file issues:
  https://github.com/georchestra/security-proxy/issues⁠

• Supported architectures:
  amd64⁠

• Source of this description:
  repo's directory⁠

⁠What is georchestra/security-proxy

Security-proxy belongs to geOrchestra core, since it is the component which :

• handles user sessions
• routes requests to webapps (except CAS)

⁠Deprecation notes

Security-proxy is deprecated in favor of Gateway⁠. It is still maintained for now, but will be removed in future versions.

⁠How to use this image

As for every other geOrchestra webapp, its configuration resides in the data directory (datadir⁠), typically something like /etc/georchestra, where it expects to find a analytics sub-directory.

It is recommended to use the official docker composition: https://github.com/georchestra/docker⁠.

For this specific component, see the section proxy in the georchestra/docker/docker-compose.yml⁠ file.

⁠Where is it built

This image is built using maven : ../mvnw package docker:build -Pdocker in georchestra repo security-proxy/ folder.

⁠License

View license information⁠ for the software contained in this image.

As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).

As for any docker image, it is the user's responsibility to ensure that usages of this image comply with any relevant licenses for all software contained within.