allawala / service-chassis Goto Github PK

When a user authenticates successfully, the token is already added to the response header. However the caller might want to store the token in an active token list. Then this list can later be consulted when checking if the user is authenticated based on the passed-in token in the request.

Invalidate either a single session or all sessions for the token subject

• make the configuration file syntax consistent
• authenticate directive should set the token principal from the authenticated subject

For the projects using the chassis, the upgraded versions of these libraries seem to add significant time to the compilation when there are quite a few enums. The time seem to be related to macro compilation.

• Simple: Issue a jwt token with a higher duration without an explicit refresh token
• Full: proper refresh token semantics (TBD)

In the hopes to get rid of the issue "knownDirectSubclasses of observed before subclass registered"
Upgrade

• scala
• circe
• enumeratum
• jwt-circe

Each individual service building upon this chassis should be able to load its own specific set of configuration along with the base common configuration

Rejection handler should log and respond with the same error envelope as the exception handler

To allow the caller to perform some action on failure for instance update login attempt count.

${ENV} environment variable will be used to determine which application and logging configuration to load. If missing, it will default to the local environment

Add foundation that provides the following and allows the extending micro services to provide more concrete auth realms

• cater for username password credentials
• cater for JWT token
• cater for refresh tokens due to remember me semantics

Create an initial project image with

• Minimal scala seed
• Add .gitignore file
• Add README.md
• Init git flow

This handles propagation across different threads