Angular 4/Angular 2 validate SPA against Azure B2C Active Directory - asp.net-mvc

In Angular 4/Angular 2 app, I want to validate it against Azure B2C Active Directory. In ASP.NET MVC, it was done using [Authorize] attribute on Controller and using an OWIN Startup.cs class to generate the authentication challenge and generating the Bearer token.
Moving on to a SPA application using Angular 4/Angular 2, I am not able to find a relevant tutorial for the same. I have seen some examples using Auth0, but I am not looking for an Auth0 solution. I want to authenticate directly against the Azure B2C Active Directory.
Can some approach and relevant example and tutorial describing the same be provided.
Tried ng2-adal sample suggested by 'Fei Xue - MSFT' below. Adding ng2-adal sample error message pics.
Added 'package.json' code:-
{
"name": "angular2-azure-ad",
"version": "1.0.0",
"scripts": {
"gulp": "gulp",
"start": "tsc && concurrently \"npm run tsc:w\" \"npm run lite\" ",
"lite": "lite-server",
"postinstall": "typings install",
"build": "tsc",
"tsc": "tsc",
"tsc:w": "tsc -w",
"typings": "typings"
},
"license": "ISC",
"dependencies": {
"#angular/common": "~4.0.0",
"#angular/compiler": "~4.0.0",
"#angular/core": "~4.0.0",
"#angular/http": "~4.0.0",
"#angular/platform-browser": "~4.0.0",
"#angular/platform-browser-dynamic": "~4.0.0",
"#angular/router": "~4.0.0",
"angular2-adal": "^0.1.4",
"angular2-in-memory-web-api": "0.0.10",
"bootstrap": "^3.3.7",
"core-js": "^2.4.1",
"rxjs": "5.0.1",
"systemjs": "0.19.40",
"zone.js": "^0.8.4"
},
"devDependencies": {
"concurrently": "^2.0.0",
"lite-server": "^2.2.0",
"typescript": "^1.8.10",
"typings": "^1.0.4",
"gulp": "^3.9.1",
"gulp-typescript": "^2.13.6",
"gulp-sourcemaps": "^1.6.0",
"gulp-shell": "^0.5.2",
"del": "^2.2.0"
}
}

AFAIK, we need to implement CanActivate interface in the Angular 2 for the guard deciding if a route can be activated.
To protect the SPA for the Angular 2 using Azure AD you can refer this code sample. And about the Azure AD B2C authentication, you can refer this document.

Related

Angular Service Workers not work on iOS standalone mode

I am working on PWA with Ionic v4 and Angular PWA service workers. On app.component.ts have a injected service to check if updates are available on PWA and then download and reload.
When I open PWA with the browser the service works fine and If I deploy an update the service worker update the cached PWA and ‘auto-reload’ the page.
The problem comes with PWA/standalone mode, on iOS when the PWA is added to homescreen it not refreshes anymore even killing it with the task app list. Only If I shutdown the device and on again it refreshes the state of the app. On Android devices all works as expected on PWA mode.
This is my version checker service implemented with Angular service worker:
import {Injectable} from '#angular/core';
import {SwUpdate} from '#angular/service-worker';
#Injectable()
export class LogUpdateService {
constructor(updates: SwUpdate) {
console.warn('check')
updates.available.subscribe(event => {
console.log('current version is', event.current);
console.log('available version is', event.available);
updates.activateUpdate().then(() => {
console.warn('downloaded')
document.location.reload();
});
});
updates.activated.subscribe(event => {
console.log('old version was', event.previous);
console.log('new version is', event.current);
});
}
}
This is my package.json:
"dependencies": {
"#angular/common": "^7.2.9",
"#angular/core": "^7.2.9",
"#angular/forms": "^7.2.9",
"#angular/http": "^7.2.9",
"#angular/platform-browser": "^7.2.9",
"#angular/platform-browser-dynamic": "^7.2.9",
"#angular/pwa": "0.13.8",
"#angular/router": "^7.2.9",
"#angular/service-worker": "7.2.12",
"#ionic-native/core": "^5.2.0",
"#ionic-native/network": "^5.2.0",
"#ionic-native/splash-screen": "^5.2.0",
"#ionic-native/status-bar": "^5.2.0",
"#ionic/angular": "4.2.0",
"#ionic/storage": "^2.2.0",
"#ngx-translate/core": "^11.0.1",
"#ngx-translate/http-loader": "^4.0.0",
"cordova-plugin-network-information": "2.0.1",
"cordova-sqlite-storage": "3.2.0",
"core-js": "^2.6.5",
"ionic2-calendar": "^0.5.2",
"moment": "^2.24.0",
"rxjs": "~6.4.0",
"serve": "^10.1.2",
"zone.js": "~0.8.29"
},
"devDependencies": {
"#angular-devkit/architect": "0.13.8",
"#angular-devkit/build-angular": "0.13.8",
"#angular-devkit/core": "7.3.8",
"#angular-devkit/schematics": "7.3.8",
"#angular/cli": "7.3.8",
"#angular/compiler": "~7.2.9",
"#angular/compiler-cli": "~7.2.9",
"#angular/language-service": "~7.2.9",
"#ionic/angular-toolkit": "1.5.0",
"#types/jasmine": "~3.3.9",
"#types/jasminewd2": "~2.0.6",
"#types/node": "~11.11.3",
"#ionic/lab": "1.0.24",
"codelyzer": "~4.5.0",
"jasmine-core": "~3.3.0",
"jasmine-spec-reporter": "~4.2.1",
"karma": "~4.0.1",
"karma-chrome-launcher": "~2.2.0",
"karma-coverage-istanbul-reporter": "~2.0.5",
"karma-jasmine": "~2.0.1",
"karma-jasmine-html-reporter": "^1.4.0",
"protractor": "~5.4.2",
"ts-node": "~8.0.3",
"tslint": "~5.14.0",
"typescript": "^3.1.6"
},
"description": "An Ionic project",
"cordova": {
"plugins": {
"cordova-sqlite-storage": {},
"cordova-plugin-network-information": {}
}
}
Any Idea with this problem?
See: PWAs on iOS 12.2 beta: the good, the bad, and the "not sure yet if good"
The only solution that I found is to code a javascript function (e.g. updateiOS()) that will do the following
1- Verify if we are running on iOS standalone mode (if not then don't continue)
2- Check for a new version on the server and reload page if we found a new version (make sure this https request is not cached!)
3- Save the last check time in a variable (e.g. var lastCheckTime)
And in my main javascript function, I will create a listener for "focus" event that will check the difference between now and lastCheckTime, if it's more than let's say 1 day then call updateiOS()
so far the focus event is working fine with me

Compilation error from Angular and typescript in VS 2015 MVC project

I am new to Angular and taking baby step to implement in ASP.Net MVC project. I downloaded the Angular quick start from github and latest typescript v 3.2.2.0 for visual studio 2015 update 3. I am getting the following error Property lift in the type 'Subject is not assignable tot he same property in base type Observable' .
other version used:
npm -v is 6.4.1
node -v is 10.15.2
The package.json that I downloaded from github had a reference to the older version version. Attached is the package.json file i am using.
I have my npm running and was able to host the website through lift-server.
error TS2416: Property 'lift' in type 'Subject' is not assignable
to the same property in base type 'Observable'. Type '(operator:
Operator) => Observable' is not assignable to type
'(operator: Operator) => Observable'. Type 'Observable'
is not assignable to type 'Observable'. Type 'T' is not assignable
to type 'R'
Please help.
Error snippet
{
"name": "angular-quickstart",
"version": "1.0.0",
"description": "QuickStart package.json from the documentation, supplemented with testing support",
"scripts": {
"build": "tsc -p src/",
"build:watch": "tsc -p src/ -w",
"build:e2e": "tsc -p e2e/",
"serve": "lite-server -c=bs-config.json",
"serve:e2e": "lite-server -c=bs-config.e2e.json",
"prestart": "npm run build",
"start": "concurrently \"npm run build:watch\" \"npm run serve\"",
"pree2e": "npm run build:e2e",
"e2e": "concurrently \"npm run serve:e2e\" \"npm run protractor\" --kill-others --success first",
"preprotractor": "webdriver-manager update",
"protractor": "protractor protractor.config.js",
"pretest": "npm run build",
"test": "concurrently \"npm run build:watch\" \"karma start karma.conf.js\"",
"pretest:once": "npm run build",
"test:once": "karma start karma.conf.js --single-run",
"lint": "tslint ./src/**/*.ts -t verbose"
},
"keywords": [],
"author": "",
"license": "MIT",
"dependencies": {
"#angular/common": "~4.3.4",
"#angular/compiler": "~4.3.4",
"#angular/core": "~4.3.4",
"#angular/forms": "~4.3.4",
"#angular/http": "~4.3.4",
"#angular/platform-browser": "~4.3.4",
"#angular/platform-browser-dynamic": "~4.3.4",
"#angular/router": "~4.3.4",
"angular-in-memory-web-api": "~0.3.0",
"systemjs": "0.19.40",
"core-js": "^2.4.1",
"rxjs": "5.0.1",
"zone.js": "^0.8.4"
},
"devDependencies": {
"concurrently": "^3.2.0",
"lite-server": "^2.2.2",
"typescript": "~2.1.0",
"canonical-path": "0.0.2",
"tslint": "^3.15.1",
"lodash": "^4.16.4",
"jasmine-core": "~2.4.1",
"karma": "^1.3.0",
"karma-chrome-launcher": "^2.0.0",
"karma-cli": "^1.0.1",
"karma-jasmine": "^1.0.2",
"karma-jasmine-html-reporter": "^0.2.2",
"protractor": "~4.0.14",
"rimraf": "^2.5.4",
"#types/node": "^6.0.46",
"#types/jasmine": "2.5.36"
},
"repository": {}
}
Try to upgrade with:
npm install --save rxjs#^6.4.0
this issue should have been fixed in RxJS 6.
There are a couple things wrong here.
First, your Typescript is on the latest version. I'm not sure even Angular 7 supports Typescript 3.2.2. I think they will when Angular 8 is released shortly.
Second, your Angular packages are way out of date. You should update to Angular 7 if possible.
Third, Visual Studio can sometimes get picky about your ts config. If the above two don't work please post your ts config so we can look at it. I build Angular Applications from the Web Form template in VS 2017. I use the Angular CLI instead of any VS Extension. If you want more details let me know.
Here's a package.json from a project I started recently:
"private": true,
"dependencies": {
"#angular/animations": "~7.1.0",
"#angular/common": "~7.1.0",
"#angular/compiler": "~7.1.0",
"#angular/core": "~7.1.0",
"#angular/forms": "~7.1.0",
"#angular/platform-browser": "~7.1.0",
"#angular/platform-browser-dynamic": "~7.1.0",
"#angular/router": "~7.1.0",
"classlist.js": "^1.1.20150312",
"core-js": "^2.5.4",
"d3": "^4.10.2",
"d3-array": "^1.2.1",
"d3-brush": "^1.0.4",
"d3-color": "^1.0.3",
"d3-force": "^1.1.0",
"d3-format": "^1.2.0",
"d3-hierarchy": "^1.1.5",
"d3-interpolate": "^1.1.5",
"d3-scale": "^1.0.6",
"d3-selection": "^1.1.0",
"d3-shape": "^1.2.0",
"d3-time-format": "^2.1.0",
"rxjs": "~6.3.3",
"tslib": "^1.9.0",
"web-animations-js": "^2.3.1",
"zone.js": "~0.8.26",
"bootstrap": "4.3.1"
},
"devDependencies": {
"#angular-devkit/build-angular": "~0.11.0",
"#angular-devkit/build-ng-packagr": "~0.11.0",
"#angular/cli": "~7.1.3",
"#angular/compiler-cli": "~7.1.0",
"#angular/language-service": "~7.1.0",
"#types/node": "~8.9.4",
"#types/jasmine": "~2.8.8",
"#types/jasminewd2": "~2.0.3",
"codelyzer": "~4.5.0",
"jasmine-core": "~2.99.1",
"jasmine-spec-reporter": "~4.2.1",
"karma": "~3.1.1",
"karma-chrome-launcher": "~2.2.0",
"karma-coverage-istanbul-reporter": "~2.0.1",
"karma-jasmine": "~1.1.2",
"karma-jasmine-html-reporter": "^0.2.2",
"ng-packagr": "^4.2.0",
"protractor": "~5.4.0",
"ts-node": "~7.0.0",
"tsickle": ">=0.29.0",
"tslib": "^1.9.0",
"tslint": "~5.11.0",
"typescript": "~3.1.6"
}
}

Docker push fails after multiple retries on a specific layer

I'm trying to push my own Docker image for an Angular 5 project that I've built. My docker image extends the well known node:carbon image and runs the following commands:
FROM node:carbon
WORKDIR /usr/src/app
COPY package.json .
COPY package-lock.json .
RUN npm install --no-optional
COPY . .
EXPOSE 8080
CMD ["npm", "start"]
The package.json file has the following content:
{
"name": "turist-front",
"version": "0.0.0",
"license": "MIT",
"scripts": {
"ng": "ng",
"start": "ng serve",
"build": "ng build",
"test": "ng test",
"lint": "ng lint",
"e2e": "ng e2e"
},
"private": true,
"dependencies": {
"#agm/core": "^1.0.0-beta.2",
"#angular-devkit/core": "^0.3.1",
"#angular/animations": "^5.0.5",
"#angular/cdk": "^5.0.0-rc.2",
"#angular/common": "^5.0.0",
"#angular/compiler": "^5.0.0",
"#angular/core": "^5.0.0",
"#angular/flex-layout": "^2.0.0-beta.11",
"#angular/forms": "^5.0.0",
"#angular/http": "^5.0.0",
"#angular/material": "^5.0.0-rc.2",
"#angular/platform-browser": "^5.0.0",
"#angular/platform-browser-dynamic": "^5.0.0",
"#angular/router": "^5.0.0",
"#ngx-translate/http-loader": "^2.0.0",
"#swimlane/ngx-datatable": "^11.1.5",
"angular-l10n": "^4.1.2",
"angular2-notifications": "^0.9.6",
"core-js": "^2.4.1",
"d3": "^4.11.0",
"hammerjs": "^2.0.8",
"material-design-icons": "^3.0.1",
"ng2-dragula": "^1.5.0",
"ngx-auth": "^3.0.0",
"ngx-dropzone-wrapper": "^5.2.0",
"ngx-perfect-scrollbar": "^5.0.1",
"ngx-quill": "^2.0.3",
"normalize.css": "^7.0.0",
"rxjs": "5.5.2",
"screenfull": "^3.3.2",
"zone.js": "^0.8.14"
},
"devDependencies": {
"#angular/cli": "1.5.5",
"#angular/compiler-cli": "^5.0.0",
"#angular/language-service": "^5.0.0",
"#compodoc/compodoc": "^1.0.4",
"#types/jasmine": "~2.5.53",
"#types/jasminewd2": "~2.0.2",
"#types/node": "~6.0.60",
"codelyzer": "^4.0.1",
"hads": "^1.5.0",
"jasmine-core": "~2.6.2",
"jasmine-spec-reporter": "~4.1.0",
"karma": "~1.7.0",
"karma-chrome-launcher": "~2.1.1",
"karma-cli": "~1.0.1",
"karma-coverage-istanbul-reporter": "^1.2.1",
"karma-jasmine": "~1.1.0",
"karma-jasmine-html-reporter": "^0.2.2",
"protractor": "~5.1.2",
"ts-node": "~3.2.0",
"tslint": "~5.7.0",
"typescript": "~2.4.2"
}
}
After I've built my image I want to push it to my docker repository. But although I've tried at least 5 times to execute the docker push command, every time it fails with the error file integrity checksum failed for. It is not always the same file that fails the integrity check and I also didn't notice any timeout behaviour or something similar.
What I have noticed is that the one layer (always the same) fails being pushed and it restarts 5-6 times unsuccessful:
cc19355015b5: Pushing [=======> ] 98.66MB/653.4MB
and than
cc19355015b5: Pushing [=======> ] Retrying in 5 seconds
I had the same issue today, then I found a typo in my ECR location, once it is corrected, the push succeeded immediately, so I believe Docker just doesn't tell you that it can't find the ECR repo and stuck in retrying.
Another way to solve this is to reduce the amount of data that are sent at a time to the registry, by breaking up the layers or using a tool like regclient that falls back to sending 1MB chunks by default if larger chunks don't succeed at first.
The steps are:
Download regctl
Save the image as a tar file
Push it to the registry using regctl
curl -L https://github.com/regclient/regclient/releases/latest/download/regctl-linux-amd64 > regctl
chmod 755 regctl
docker save <imagename> > image.tar
./regctl image import <imagename> image.tar -v debug
The chunk size can be configured. See this answer for more in-depth details.

Angular 5 app not working in ios8 (Browserstack)

I've tested my Angular 5 app on an iPhone 6 running IOS8 (Safari) and in Browserstack. The angular app doesn't run, I just get an empty page and this Javascript error.
Any suggestions?
This is my package.json file. I'm thinking that some package that I added here is causing some conflict and preventing the app from displaying. Previously I had the app able to run in IOS8, but that was with Angular 4.4 and I wasn't using mdbootstrap library.
{
"name": "XXXX",
"version": "1.0.0",
"license": "MIT",
"scripts": {
"ng": "ng",
"start": "ng serve",
"build": "ng build",
"test": "ng test",
"lint": "ng lint",
"e2e": "ng e2e",
"i18n": "ng-xi18n"
},
"private": true,
"dependencies": {
"#agm/core": "^1.0.0-beta.2",
"#angular-devkit/schematics": "0.0.34",
"#angular/animations": "^5.0.3",
"#angular/common": "^5.0.3",
"#angular/compiler": "^5.0.3",
"#angular/core": "^5.0.3",
"#angular/forms": "^5.0.3",
"#angular/http": "^5.0.3",
"#angular/platform-browser": "^5.0.3",
"#angular/platform-browser-dynamic": "^5.0.3",
"#angular/router": "^5.0.3",
"applicationinsights-js": "^1.0.8",
"bootstrap": "^3.3.7",
"bootstrap-select": "^1.12.4",
"chart.js": "^2.5.0",
"core-js": "^2.4.1",
"easy-pie-chart": "^2.1.7",
"font-awesome": "^4.7.0",
"hammerjs": "^2.0.8",
"jquery": "^3.2.1",
"libphonenumber-js": "^0.4.40",
"ng-autosize": "^1.1.0",
"ng-mdb-pro": "XXXX",
"npm-check-updates": "^2.13.0",
"rxjs": "^5.4.2",
"screenfull": "^3.3.0",
"zone.js": "^0.8.14"
},
"devDependencies": {
"#angular/cli": "^1.5.5",
"#angular/compiler-cli": "^5.0.3",
"#angular/language-service": "^4.3.0",
"#types/applicationinsights-js": "^1.0.2",
"#types/jasmine": "~2.8.2",
"#types/jasminewd2": "~2.0.2",
"#types/node": "~6.0.60",
"codelyzer": "~4.0.1",
"jasmine-core": "^2.8.0",
"jasmine-spec-reporter": "~4.2.1",
"karma": "~1.7.0",
"karma-chrome-launcher": "~2.2.0",
"karma-cli": "~1.0.1",
"karma-coverage-istanbul-reporter": "^1.2.1",
"karma-jasmine": "~1.1.0",
"karma-jasmine-html-reporter": "^0.2.2",
"karma-junit-reporter": "^1.2.0",
"protractor": "~5.2.0",
"ts-node": "~3.3.0",
"tslint": "^5.3.2",
"typescript": ">=2.4.2 <2.5.0"
}
}
Had a similar problem. It should be resolved by providing correct polyfills.
you can find browser support info here https://angular.io/guide/browser-support
If you use JIT compiler (not AOT) then safari needs at least ES7 reflect polyfill.
Safari 7 & 8 need also ES6
If you still use the old intl based pipes then do not forget to include them.
For older browsers core-js/es/... imports usually resolve the issues.
Go to your src/polyfills.ts and enable desired polyfills.
There is also a fetch polyfill mentioned in the readme of the generated project, that is not included in polyfill.ts.
import 'whatwg-fetch'; // Run `npm install --save whatwg-fetch`
$ ng build --mangle safari10=true --prod
Follow the next steps
Execute command to generate file .browserslistrc
npx browserslist
Into the file set the last version until you get that you need, in my case I need work with safari 10, then i set the file ".browserslistrc" :
last 2 Chrome version
last 2 Firefox version
last 2 Edge major versions
last 5 Safari major versions
last 5 iOS major versions

: starting container process caused "exec: \"sudo\": executable file not found

ERROR:Cannot start service cpanel_client: invalid header field value "oci runtime error: container_linux.go:247: starting container process caused "exec: \"sudo\": executable file not found
Here is my docker file,
FROM node:8.1.2-alpine
WORKDIR /control-panel
COPY package.json /control-panel/package.json
RUN npm install auth0-lock mapbox-gl mapbox-gl-geocoder tinymce angular2-jwt aws-sdk #angular/cli hammerjs jquery moment moment-timezone bootstrap#3 jquery-ui-dist --save
RUN mv /control-panel/node_modules /node_modules
COPY . /control-panel
EXPOSE 4200
EXPOSE 49153
here is the docker compose.yml,
cpanel_client:
build: .
ports:
- "4200:4200"
- "49153:49153"
volumes:
- .:/control-panel
command: npm start
my package.json file,
{
"name": "cpanelcli",
"version": "0.0.0",
"license": "MIT",
"angular-cli": {},
"scripts": {
"ng": "ng",
"start": "ng serve --host 0.0.0.0",
"lint": "tslint \"src/**/*.ts\"",
"test": "ng test",
"pree2e": "webdriver-manager update --standalone false --gecko false",
"e2e": "protractor"
},
"private": true,
"dependencies": {
"#angular/common": "4.0.0",
"#angular/compiler": "4.0.0",
"#angular/core": "4.0.0",
"#angular/forms": "4.0.0",
"#angular/http": "4.0.0",
"#angular/material": "^2.0.0-beta.2",
"#angular/platform-browser": "4.0.0",
"#angular/platform-browser-dynamic": "4.0.0",
"#angular/router": "^3.3.1",
"#types/jquery": "^2.0.46",
"angular2-jwt": "^0.1.28",
"aws-sdk": "^2.28.0",
"bootstrap": "^3.3.7",
"core-js": "^2.4.1",
"hammerjs": "^2.0.8",
"jquery": "^3.2.1",
"jquery-ui-dist": "^1.12.1",
"mapbox-gl": "^0.34.0",
"mapbox-gl-geocoder": "^2.0.1",
"mapbox.js": "^3.0.1",
"ng2-datepicker": "^1.8.0",
"rxjs": "^5.0.1",
"tinymce": "^4.5.5",
"ts-helpers": "^1.1.1",
"zone.js": "^0.7.2"
},
"devDependencies": {
"#angular/compiler-cli": "^2.3.1",
"#types/jasmine": "2.5.38",
"#types/node": "^6.0.42",
"angular-cli": "1.0.0-beta.24",
"codelyzer": "~2.0.0-beta.1",
"jasmine-core": "2.5.2",
"jasmine-spec-reporter": "2.5.0",
"karma": "1.2.0",
"karma-chrome-launcher": "^2.0.0",
"karma-cli": "^1.0.1",
"karma-jasmine": "^1.0.2",
"karma-remap-istanbul": "^0.2.1",
"protractor": "~4.0.13",
"ts-node": "1.2.1",
"tslint": "^4.0.2",
"typescript": "~2.0.3"
}
}
Build was successful. I get this errror when i run docker-compose run –rm cpanel_client ng init –skip-npm –name CliDemo.
can someone tell me where am i wrong?
The node_modules/.bin folder is not in $PATH by default. You need to just call the path directly:
command: /control-panel/node_modules/.bin/ng serve --host 0.0.0.0
It appears sudo is not installed on your image. Note the error message:
"exec: \"sudo\": executable file not found
Something is trying to sudo ("super-user do") a thing, and can't. Try installing sudo via the package manager to appease that step, or try configuring that step to not require super user permissions.

Resources