Using a container

To begin using JOSSO, you have several options for container tools, including Docker, Containerd, and Kubernetes. In this example, we will demonstrate how to use Docker to start JOSSO. However, you can choose to use any other container tool that you prefer.

docker run \
        --name josso-ee \
        --detach \
        --env JOSSO_CLIENT_ID="idbus-f2f7244e-bbce-44ca-8b33-f5c0bde339f7" \
        --env JOSSO_CLIENT_SECRET="7oUHlv(HLT%vxK4L" \
        --env JOSSO_ADMIN_USR=myadmin \
        --env JOSSO_ADMIN_PWD=changeme \
        --env JOSSO_SKIP_ADMIN_CREATE=false \
        -p8081:8081 -p8101:8101 \
        atricore/josso-ee:latest

Environment Variables

JOSSO_CLIENT_ID: client id to be used to connect to the server using the terraform plugin
JOSSO_CLIENT_SECRET: secret to be used to connect to the server using the terraform plugin
JOSSO_ADMIN_USR: optional, the server will create an administrator user to allow ssh access.
JOSSO_ADMIN_PWD: optional, the password for the administrator user
JOSSO_SKIP_ADMIN_CREATE: optinal, JOSSO server will only create the administrator user if this flag is set to FALSE.

Network Ports

8081: Default JOSSO server HTTP port.
8101: optional, JOSSO server SSH service port.

Persisting configuration

To ensure that any changes you make to the JOSSO server's configuration are retained after the server is shut down or restarted, you can use volume mapping to persist the configuration. This involves mapping certain server folders to a volume, which allows the server to store the configuration changes in the volume.

Server configuration

Contains configuration files for different server components. (logging, HTTP server, SSH server, DB store, etc)

/opt/atricore/josso/etc

Server internal store

Internal derby DB storage.

/opt/atricore/josso/data/derby