We shouldn't log the github user, and we shouldn't add the username to the sub since engine will log the sub from JWT.
The proposal is to add a counter instead to the sub part of the JWT, and perhaps not save the username at all.

Every 2 hours we are getting an error from redis. See the attached pictures.
This is now an issue due to login after some delay. If the enviroment is ideal for more than 2 hours, the login will fail at first attempt, and then it will work.

Enable passing docker secrets by implementing the recommended way from Docker.

Follow the guide of how to enable docker secrets support from docker: https://docs.docker.com/engine/swarm/secrets/#build-support-for-docker-secrets-into-your-images

Add information what this repo is, and how to use it.

Security scan found three vulnerabilities: https://cloud.docker.com/app/qlikea/repository/registry-1.docker.io/qlikea/qliktive-authentication-service/tags/0.0.1-49

Two of these are from our base image, we may want to use node:8 which I believe these are fixed in.

The last one comes from bash that we are installing in Dockerfile.

This issue contains a checklist of tasks that is needed before repo can be open sourced.

Checklist

• LICENSE file added to repo with a MIT license.
• Update package.json with the right info for author, description, license and name.
• Linting of code e.g. airbnb for node.js repo.
• Circle CI build to secure quality e.g. linting, tests, docker image.
• Update README.md to contain relevant info for the repo e.g. Contributions
• Add .editorconfig, .gitignore and .gitattributes

Rename endpoints to something more intuitive like sign-in or sign-out or make them CRUDified with create and destroy

Document how to setup an app on github, and how it can be used as an IDP.

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: Preset name not found within published preset config (monorepo:babel6). Note: this is a nested preset so please contact the preset author if you are unable to fix it yourself.

A BlackDuck Protex scan failed on this repository.

Number of files needing identification: 1

If you are unsure how this process works, please contact trunk team on Slack.

No more automated issues will be created on this repository until this issue
is closed.

Please prioritize and solve this as soon as possible. If the files
has been identified already, you may ignore and close this issue.