Home

AAD Application Proxy and B2B Users

%3CLINGO-SUB%20id%3D%22lingo-sub-456673%22%20slang%3D%22en-US%22%3EAAD%20Application%20Proxy%20and%20B2B%20Users%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-456673%22%20slang%3D%22en-US%22%3E%3CP%3EUsing%20Application%20Proxy%20for%20internal%20program%20which%2C%20after%20user%20inputs%20credentials%2C%20calls%20an%20API%20which%20is%20complaining%20because%20CORS%20cannot%20find%20the%26nbsp%3BAccess-Control-Allow-Origin%20header.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20ideas%20on%20how%20to%20either%3A%3C%2FP%3E%3CP%3E1%20-%20Disable%20CORS%20on%20the%20API%20site.%3C%2FP%3E%3CP%3E2%20-%20Auto%20add%20the%20header%20which%20is%20apparently%20stripped%20by%20Application%20Proxy%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-456673%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20AD%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
DrBob
Occasional Visitor

Using Application Proxy for internal program which, after user inputs credentials, calls an API which is complaining because CORS cannot find the Access-Control-Allow-Origin header. 

 

Any ideas on how to either:

1 - Disable CORS on the API site.

2 - Auto add the header which is apparently stripped by Application Proxy