https://github.com/shadowblack77/nestjs-auth-project

Repository with full auth project for base to build projects with authorization & authentcation
https://github.com/shadowblack77/nestjs-auth-project

authentication authorization hbs mailer nestjs nodejs oatuh2 passportjs security typeorm typescript

Last synced: 6 days ago
JSON representation

Repository with full auth project for base to build projects with authorization & authentcation

• Host: GitHub
• URL: https://github.com/shadowblack77/nestjs-auth-project
• Owner: ShadowBlack77
• License: mit
• Created: 2025-01-23T22:54:42.000Z (22 days ago)
• Default Branch: main
• Last Pushed: 2025-02-06T17:11:19.000Z (8 days ago)
• Last Synced: 2025-02-06T18:26:55.153Z (8 days ago)
• Topics: authentication, authorization, hbs, mailer, nestjs, nodejs, oatuh2, passportjs, security, typeorm, typescript
• Language: TypeScript
• Homepage:
• Size: 455 KB
• Stars: 1
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        


  



[circleci-image]: https://img.shields.io/circleci/build/github/nestjs/nest/master?token=abc123def456

[circleci-url]: https://circleci.com/gh/nestjs/nest

  
A progressive Node.js framework for building efficient and scalable server-side applications.

    


















  

    

  



 

## Run Project

- npm run start

- npm run start:dev

- npm run start:prod


## App Features

- Login via email & password

- login via Google

- Authorization & Authentication via JWT & Refresh Tokens

- Email Verification

- Possibility to enable 2FA

- Reset Password

- You can log in 3 times, if you make a mistake 3 times, you will be blocked for 15 minutes

- SessionID and short-time tokens for email and 2FA verification

- Limitation of the number of queries/per minute

- API Key

- Email templates with HBS

## How to develop the application further?

Using the current database containing all the most important authorization and authentication elements, you can develop the application in any way you want! However, I recommend a modular approach to avoid unnecessary chaos in the design, what do I mean? If you plan to add a Todos or products section, create a module, e.g. features, and then add submodules, e.g. todos. If you would like to see an example of such an architecture, see my other project: nestjs-ecommerce-api