Feature Request

onSignUpEvent when a new user signs up in the application.

Description

Create an event and an entity in the event store when a new user signs up. This entity will register the user with relevant data so that it is not necessary to create it using a command after the sign-up.

Possible Solution

Create the event in the event-store DynamoDB table as the last step in the signup process. Look how it is done in the kafka consumer or the storage rockets. The event could look like:

@Event
export class UserInfoCreated {
  public constructor(
    public id: string,
    readonly email: string,
    readonly phone: string,
    readonly role: AppRole,
    readonly isDeleted: boolean
  ) {}

Additional information

Documentation bug, improvement

Description

Document the procedure to change an user forgotten password.

Feature Request

Description

Currently, the user gets an accessToken (necessary to sign out) and an idToken (necessary to access restricted resources).
It would be great to unify both tokens, so the API would be cleaner and less confusing.

Bug Report

In order to use the tokenVerifier object in the config, generated in the Auth rocket, in other rockets, the rolesClaim field need to be set as well as the issuer and the jwksUri

Current Behavior

Only issuer and the jwksUri are set in the tokenVerifier object

Expected behavior

rolesClaim is added as well to the tokenVerifier object

Possible Solution

PR

Additional information

Environment

• Booster version: 0.16.2
• Node/npm version: latest
• OS: [e.g. OSX 10.13.4, Windows 10]

Right now, if we decide to create a role without sign-up method, the user has to manually create the user with its role in AWS. The idea is to automate this so a user can run a script like ./createUser <user_pool_id> <user_email> <role> and the user sets up automatically. Leaving more info below:

This affect these kind of roles (no sign-up methods):

@Role({
  auth: {
    signUpMethods: [],
  },
})
export class Admin {}

To sign in, the user has to manually create a user:

1. Go to AWS console (cognito)
2. Create the user with a temporary password
3. Run the following command to set a permanent password:

aws cognito-idp admin-set-user-password
  --user-pool-id <your-user-pool-id> \
  --username <username> \
  --password <password> \
  --permanent

4. Run this other command to add the custom:role = Admin:

 aws cognito-idp admin-update-user-attributes \
    --user-pool-id <pool_id> \
    --username <username>  \
    --user-attributes Name="custom:role",Value="Admin"

Bug Report

Current Behavior

When the project name + lambda name is +64 characters, the deployment fails:

It's also happening for other lambdas, but this one is an example.

Possible Solution

We could shorten the lambda name.

Environment

• Booster version: 0.20.0
• Node/npm version: 16.2

Documentation bug, improvement

Description

The tokenId is missing from the sign-in response and the refresh token response.