firely/auth repository overview

Firely Auth is an OAuth2 server providing token with claims conformant to SMART on FHIR⁠.

The easiest way to run a Firely Auth in a Docker container is to run it with a SQLite repository. This is also the default mode.

You need a license to run a Firely Auth. You can download an evaluation license file from the fire.ly⁠⁠ website. The license file is by default named firelyserver-license.json. Save this file to your working directory and renamed it into firely-auth-license.json.

You can provide the license to Firely Auth in two ways:

• By mounting the file to Firely Auth's working directory in the container, as shown below.
• By providing the contents of the file as a single string in an environment variable called FIRELY_AUTH_License__LicenseString.

In order to connect Firely Auth with Firely Server, you would need to create a custom appsettings file, called appsettings.instance.json as described in the doc⁠

Next is to run a container. Open your favorite command line tool and navigate to your working directory and type the command:

In Powershell: $ docker run -d -p 5100:5100 --name firely.auth -v ${PWD}/firely-auth-license.json:/app/firely-auth-license.json -v ${PWD}/appsettings.instance.json:/app/appsettings.instance.json firely/auth:latest

Or when you are using a Command Prompt: $ docker run -d -p 5100:5100 --name firely.auth -v %CD%/firely-auth-license.json:/app/firely-auth-license.json -v %CD%/appsettings.instance.json:/app/appsettings.instance.json firely/auth:latest

This will spin up a Firely Auth container. It maps the host port 5100 to the container port 5100 with the switch -p 5100:5100. It will give the container the name firely.auth with the switch --name firely.auth. Furthermore it mounts the license file from the host to the container. At last it will run the container in background mode with the switch -d.

Open a browser and use the address http://localhost:5100/⁠⁠. This will show the landing page of Firely Auth.

Further documentation is on the Firely Auth documentation pages⁠⁠, and specifically on the deployment pages⁠⁠.