Posts

Azure - website publish fail due to path long

Add below code to PropertiesGroup in .csproj file. <IntermediateOutputPath> ..\Temp </IntermediateOutputPath>

Solved: MSAL with Angular2 : Refused to display in a frame because it set 'X-Frame-Options' to 'deny'

MSAL with Angular2 : Refused to display in a frame because it set 'X-Frame-Options' to 'deny' we get this error when you are not setting redirectUri in your loginRedirect or acquireTokenRedirect methods in your angular or js code. Solution : Add redirectUri in (loginRedirect or acquireTokenRedirect) methods or at msal configuration level. editProfile() { var  authority =  `https:// ${ Domain } /tfp/ ${ tenant } / ${ profileEditPolicy } ` ;      /* just calling acquiretokenRedirect with different policy and authority            to edit profile,           no need to pass redirectUri as authority will decide */      this .authService.acquireTokenRedirect({       scopes: [Scopes], // https://yourApp.b2clogin.com/yourApp....

Solved: redirect_uri_mismatch Azure AD B2C with angular using MSAL || MSAL Profile Edit

Profile Edit in MSAL if you are using msal in Angular Application and trying to edit profile then follow below steps. 1. Set the Profile edit policy and  prepare authority. 2. Set redirectUri at the configuration level or here in below code. if you do not set the redirectUri you will get this error : "MSAL with Angular2 : Refused to display in a frame because it set 'X-Frame-Options' to 'deny'" 2. Call acquireTokenRedirect as below.  editProfile() { var  authority =  `https:// ${ Domain } /tfp/ ${ tenant } / ${ profileEditPolicy } ` ;      /* just calling acquiretokenRedirect with different policy and authority       to edit profile,      no need to pass redirectUri as authority will decide */      this .authService.acquireTokenRedirect({      ...

cannot read property 'subscribe' of undefined in Angular

cannot read property 'subscribe' of undefined in Angular You will get this error when you initialize the subject as below. public  tokenAcquired: Subject<any>; and calling subscribe method over it as below. this .appService.tokenAcquired.subscribe((token)  =>  {        this .getApps();     }) Solution - To fix this error declare and initialize the subject as below. public  tokenAcquired: Subject<any> =  new  Subject<any>(); Thanks QFLES

Invalid state. ''bad, state expected : null. in msal Angular

When you are using MSAL in angular app you encounter this error "Invalid state. ''bad, state expected : null" while calling " getCachedTokenInternal " method.  Typescript shows pass string in intelligence and if you are now aware about state then you will pass blank string like "" but it gives above error.  Solution Pass the state as "null" as below. var  token =  super .getCachedTokenInternal(scopes,  this .getAccount(),  null ); For more refer git error explanation - Invalid state Expected: null Thanks QFLES

export 'ɵɵdefineInjectable' was not found in '@angular/core' Fixed

Error -   export 'ɵɵdefineInjectable' was not found in '@angular/core' Root Cause - when we inject the service at both places in service @Inectable({providedin:root}) and in module provider also , then we face this error. @Injectable({   providedIn:  'root' }) export   class  NgxAuthService  extends  UserAgentApplication {} and in module we are registering service in provider as below. providers: [         { provide: MSAL_CONFIG, useValue: config }, NgxAuthService,       { provide: WindowWrapper, useValue: window }       ] Solution - replace above  service class code as below. @Injectable() export   class  NgxAuthService  extends  UserAgentApplication {

System.Net.Http.HttpClient' does not contain a definition for 'PostAsJsonAsync

Error: 'System.Net.Http. HttpClient '  does not contain a definition for 'PostAsJsonAsync ' and  no  extension method ' PostAsJsonAsync ' accepting a first argument of type 'System.Net.Http. HttpClient ' could be found Solution:  You need to add a reference to System . Net . Http . Formatting . dll This can be found in the extensions assemblies area. A good way of achieving this is by adding the NuGet package  System.Net.Http.Formatting.Extension  to your project. Faced this problem in  QFLES