Currently working with a customer that has a pretty esoteric configuration for publishing some apps that use ADFS and ADFS is also published but in a non-standard way. They are publishing ADFS Proxies via UAG. Long story but bottom line this is working on
existing apps but now we need to publish a new SharePoint site that will leverage an existing ADFS instance for SSO. Everything looks good until the user is redirected back to the SharePoint app and an error is thrown in the browser stating "The upload
is blocked because the request does not contain a content-type header"
The application was then set to allow Post requests without a content-type header as shown below:
But this does not fix the issue. When the error is encountered if the user types in the SharePoint url again they are logged on (through UAG) and have access to their data in SharePoint. So something is getting blocked/loss in the redirect back to SharePoint from ADFS. Anyone ran into anything like this before?
Steve Angell - IAM Practice Director http://www.InfraScience.com)