Closed billvolt closed 5 months ago
@billvolt is your redirectURI properly configured ONLY as a SPA redirect URI?
@billvolt is your redirectURI properly configured ONLY as a SPA redirect URI?
Thanks for your question, @hectormmg. I believe I do have the redirectURI properly configured as a SPA redirect URI. In the ADFS Application Group, in the Native Application, I have included http://localhost:4200
.
@billvolt is your redirectURI properly configured ONLY as a SPA redirect URI?
Hello @hectormmg. I'm writing to follow up. I replied to your question about the redirect URL. Are you able to provide any further input on this?
Core Library
MSAL.js (@azure/msal-browser)
Core Library Version
14.10.0
Wrapper Library
MSAL Angular (@azure/msal-angular)
Wrapper Library Version
3.0.17
Public or Confidential Client?
Public
Description
When configured for ADFS, this sample shows failures on the Edge developer console.
Error Message
MSAL Logs
Network Trace (Preferrably Fiddler)
MSAL Configuration
Relevant Code Snippets
Reproduction Steps
Download MSAL from
https://github.com/AzureAD/microsoft-authentication-library-for-js
toC:\Users\myuser.mydomain\Documents\GitHub\microsoft-authentication-library-for-js
Configure sample for ADFS authority, Client ID, and trace logging.
C:\Users\myuser.mydomain\Documents\GitHub\microsoft-authentication-library-for-js\lib\msal-browser>npm run build:all
C:\Users\myuser.mydomain\Documents\GitHub\microsoft-authentication-library-for-js\samples\msal-angular-v3-samples\angular16-sample-app>npm start
Using Edge, access
http://localhost:4200/
Click Login, Login using Redirect.
Expected Behavior
Edge console should show neither CORS error nor msal:loginFailure.
It should fail to access user profile via Microsoft Graph. My intent is to replace that call with one to an ADFS-protected Web API.
Identity Provider
ADFS
Browsers Affected (Select all that apply)
Edge
Regression
N/A
Source
External (Customer)