nestjs-api-boilerplate
angular-spa-sample
nestjs-api-boilerplate | angular-spa-sample | |
---|---|---|
1 | 2 | |
121 | 28 | |
- | - | |
0.0 | 4.0 | |
about 4 years ago | about 1 month ago | |
TypeScript | TypeScript | |
- | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
nestjs-api-boilerplate
-
question on how to build a login system
ok so a couple of solutions. Azure(Requires Azure AD), Firebase(good cloud), AWS all have authentication solutions which are pretty simple to implement. Alternatively you can try using Okta/Auth0 which is a super simple solution. Then there are on-prem solutions like your own Identity Server 4 server. Then there are some good node solutions like https://docs.nestjs.com/security/authentication sounds like this is a solid place to start for you https://github.com/MidoAhmed/nestjs-api-boilerplate
angular-spa-sample
-
Keycloak: Open-Source Identity and Access Management
There is a document meant for best practices for browser-based apps such as SPA/PWA, which includes use of code flow.
https://datatracker.ietf.org/doc/html/draft-ietf-oauth-brows...
(disclaimer - co-author)
The catch is that since the client web origin and AS web origin are often different sites, the AS has to actually implement CORS on their token endpoint.
Some implementations unfortunately (perhaps due to a misunderstanding about what CORS is meant to accomplish) make this a per-tenant/per-installation allowlist of origins on the AS.
Auth0 and Ping Identity (my employer) document CORS settings for products. I'm not sure about AWS and you might need to add CORS via API gateway. Azure AD supports CORS for the token endpoint, but they may limit domains in some manner (such as redirect uri of registered clients).
FWIW, I created a demo ages ago (at https://github.com/pingidentity/angular-spa-sample), which by default is configured to target Google for OpenID Connect and uses localhost for local development/testing. It hasn't aged particularly well in terms of library choices, but I do keep it running.
A deployment based on older Angular is also at https://angular-appauth.herokuapp.com to try - IIRC I used a node server just to deal with wildcard path resolution of the index file, but there's otherwise no local logic.
-
question on how to build a login system
oh well you alrady have a provider then! here is the boilerplate to integrate with ping https://github.com/pingidentity/angular-spa-sample
What are some alternatives?
nest-rest-mongo-boilerplate - NestJs MongoDB Rest API Boilerplate
pingone-node-sdk - PingOne Node SDK
fastapi-starter - A FastAPI based low code starter/boilerplate: SQLAlchemy 2.0 (async), Postgres, React-Admin, pytest and cypress
fusionauth-localization - FusionAuth translations
nestjs-boilerplate - NestJS boilerplate. Auth, TypeORM, Mongoose, Postgres, MongoDB, Mailing, I18N, Docker.
keycloak-ui - keycloak-ui repo is moved.
express-typescript-skeleton - ๐ฐ๐ฆธ Template to start developing a REST API with Node.js (Express), TypeScript, Ts.ED, ESLint, Prettier, Husky, Prisma, etc.
spring-authorization-server - Spring Authorization Server
nestjs-microservices - ๐ Fully managed Microservices starter pack using NestJs, RabbitMQ, Kong api gateway, MongoDB, PostgreSQL, Grafana, Loki, Fluentbit.
keycloak-demo
typescript-express-starter - ๐ Quick and Easy TypeScript Express Starter
OpenID - OpenID Certifiedโข OpenID Connect Relying Party implementation for Apache HTTP Server 2.x