feat(session-management): WRK-11 Session management #6

[Krr0ptioN]

Description

Session management module and lots of refactors to make session management easier to implement

Refactors and changes

• Authentication module is splitted into three more module: PasswordModule, TokensModule, PasswordResetModule

• Users library is moved to core group folder from domain folder

• Ip Detector Library: geolocation and ip intelligence library to identify clients

• Device Detection Library: detecting client device informatoin from user-agent

• Pino logger

API Changes

Session Management

• GET /users/:id/sessions - Retrieving the sessions of the user with 'id'
• GET /@me/sessions - Retrieving the sessions of the authenticated user
• DELETE /sessions/:id - Delete the session
• POST /sessions/:id/revoke - Revoke a user's session

Checklist

• My code follows the code style of this project.
• I have added tests (stories, interaction tests, unit tests, e2e tests) to cover my changes.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.

Related Issues

Closes #6

• Session based login management #6

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
goran	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 18, 2024 9:30pm

[gitguardian]

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
10823152	Triggered	Company Email Password	3a5edd0	libs/core/security/src/lib/password/application/services/password.service.spec.ts	View secret
10823152	Triggered	Company Email Password	64e58c6	libs/core/security/src/lib/authentication/application/services/password/password.service.spec.ts	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[sonarcloud]

Quality Gate passed

Issues
27 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud