This sample demonstrates how to add authentication to an Angular application using Auth0's Lock widget from the hosted login page. The sample uses the Angular CLI.
If you haven't already done so, sign up for your free Auth0 account and create a new client in the dashboard. Find the domain and client ID from the settings area and add the URL for your application to the Allowed Callback URLs box. If you are using the server provided by the Angular CLI, that URL is http://localhost:4200
.
Clone the repo or download it from the Angular quickstart page in Auth0's documentation. Install the Angular CLI and the dependencies for the app.
npm install -g @angular/cli
cd 01-Login
npm install
If you download the sample from the quickstart page, it will come pre-populated with the client ID and domain for your application. If you clone the repo directly from Github, rename the auth0-variables.ts.example
file to auth0-variables.ts
and provide the client ID and domain there. This file is located in src/app/auth/
.
NOTE: auth0-variables.ts
has been added to .gitignore...have to cd into file and ``
NOTE: auth0-variables.ts
has been added to .gitignore...have to cd into file and `cat auth0-variables.ts ` to read/see variables and their values.
The development server that comes with the Angular CLI can be used to serve the application.
npm start
The application will be served at http://localhost:4200
.
Auth0 helps you to:
- Add authentication with multiple authentication sources, either social like Google, Facebook, Microsoft Account, LinkedIn, GitHub, Twitter, Box, Salesforce, amont others, or enterprise identity systems like Windows Azure AD, Google Apps, Active Directory, ADFS or any SAML Identity Provider.
- Add authentication through more traditional username/password databases.
- Add support for linking different user accounts with the same user.
- Support for generating signed Json Web Tokens to call your APIs and flow the user identity securely.
- Analytics of how, when and where users are logging in.
- Pull data from other sources and add it to the user profile, through JavaScript rules.
- Go to Auth0 and click Sign Up.
- Use Google, GitHub or Microsoft Account to login.
If you have found a bug or if you have a feature request, please report them at this repository issues section. Please do not report security vulnerabilities on the public GitHub issue tracker. The Responsible Disclosure Program details the procedure for disclosing security issues.
This project is licensed under the MIT license. See the LICENSE file for more info.
` nvm use 8.9 ` //NVM Node version manager
Create Angular router guard (https://angular.io/guide/router#milestone-5-route-guards):
https://github.com/auth0/angular2-jwt/tree/v1.0
https://medium.com/@ryanchenkie_40935/angular-authentication-using-route-guards-bf7a4ca13ae3
ng g guard guard/auth --module app.module
ng build
heroku create angular-auth-with-anim
- From existing repo:
heroku git:remote -a angular-auth-with-anim
heroku config:add NODE_ENV=production
git add .
git commit -m "ng build"
git push -u origin master
git push heroku master
https://angular-auth-with-anim.herokuapp.com/
heroku logs --tail
heroku addons:create mongolab
heroku config:get MONGODB_URI
mongodb://dbuser:dbpass@host:port/dbname
-
To view/run auth0 locally, must switch callbackURL to localhost via
src/app/autho0-variables.ts
...file is hidden via .gitignore...cd into directory and use Vim or Atom to modify.- Run
npm run build
+npm run serve
-
set
callbackURL: 'http://localhost:7777'
//ie., to run locally vianpm run serve
..after runningnpm run build
-
set back to
callbackURL:'https://angular-auth-with-anim.herokuapp.com'
before running/re-deploying back to Heroku
- Run
snyk test
- Run
snyk wizard
to explore remediation options
-OR-
nsp check
-
npm install --save rxjs@6
-
npm install --save rxjs-compat
-
npm install -g @angular/cli@latest
//global install
-
Angular CLI V6 requires
Node V 8.9+
:-
nvm install node --version 8.9
-
nvm use <node-version>
-
npm install @angular/cli@latest
// --save?? -
ng update @angular/cli
//from within project directory- new
angular.json
file is generated replacing the old.angular-cli.json
- new
-
now analyze existing project to check for outdated libraries:
-
ng update
-
ng update @angular/core
-
-
delete
node_modules
+package-lock.json
file in your project and re-runnpm install
if facing issues after updating
-
- ` docker-compose build `
- ` docker-compose up `//from w/in project directory
` docker-compose down `//stop and remove containers
` docker-compose down --rmi all --volumes `//stop and remove images AND volumes
` docker-compose stop `//just stop, but don't remove anything
` docker-compose logs `//get all associated activity for containers linked with this docker-compose
- For editing locally in Docker shell change auth0 url to
localhost
, and the DB connection strings inroutes/api.js
+data/load-sample-data.js
tomongodb
instead oflocalhost
in connection string(s)
` docker exec -it <container> sh `//enter container shell
` apt-get update `
` apt-get install vim `
` vim <file_name> `//open file via Vim/Bash
` i ` //insert mode
` :w! `//write/save
` :q! ` //exit/quit Vim
` docker login `
` docker tag angularnodeapp <your_dockerhub_name>/angularnodeapp `
` docker push <your_dockerhub_name>/angularnodeapp `
` npm run sample `
` npm run blowitallaway `
` snyk test `
- OR
` npm audit `
` npm audit fix `