macielti / porteiro Goto Github PK

We need to reimplement the porteiro.db.datomic.user/insert-user-with-contact! for Datalevin database.

A Contact entity will be a general entity to deal with different methods of contacting a user.

• Email
• Telegram

Add a Docker Image publish Github action step.

We need to reimplement the porteiro.db.datomic.user/insert! for Datalevin database.
This task also contemplates the lookup function.

"clift cloft Still, a porta se abriu!" - Porteiro

https://wikicasteloratimbum.fandom.com/pt-br/wiki/Porteiro

Get the user info from the JWToken instead of making a query to the database to get the roles information.

From the JWToken I want to be able to know what is the usernames of the user that the token represents.

What about if we want to drop some roles from a user instantly? The user will remain in possession of the roles while the current JWToken is valid and not expired.

If we want the roles update operation to affect users instantly we should think in a way of having a service responsible for validating JWToken sessions, so the user-identity interceptor of every service should verify the JWToken using this service before letting it go.

This can have its cons and pros. One pro is that we will be able to expire JWToken sessions actively instead of having to wait for the expiration time passively. One con is that we would have to make an HTTP call to the JWToken session verification for every time that we need to use the info stored in JWTokens.

I think that one HTTP call is a fair price to pay for the guarantee and access-control benefits that it will enable us to have.

When a user account is created we need to send an email with information about how to set up a Telegram contact.

Based on:

The role information should be inside the JWToken login result.

While authenticating the customer should be able to authenticate himself using the email or username.

Since we don't have an endpoint to create an admin user if we are not an admin first, we need to have a way of setting a default admin user in the settings file.

The healthy check endpoint should require authentication?

I am thinking about requiring a JWT token to get the healthy status of the service.

When a user creates an account, the service should already do an authentication process returning a valid auth token.