ADFS Issues since February’s CU

Topic

New Reply

Good Morning all,

Back in March, we released the February CU KB4537764 onto our Server 2016 Web Servers, following this, a customer of ours had issues accessing our site via ADFS.

The error they would see when redirected was;

Bad Request – Header field too long – HTTP Error 400. A request header field is too long

The issue wasn’t related to the customers ADFS Server, but to our WebServer. We had a good investigation and decided to rollback, which resolved the issue.

We come to this month and after searching high and low could not see any other closely resembled issue between March and April, so thus we released the March CU, again, the issue returned.

Has anyone encountered a problem with SSO and token size following Februarys CU?

I’m trying to raise a fault with Microsoft but its difficult. The Business support page doesn’t work.

Thanks!

1 user thanked author for this post.

woody

Reply | Quote

Replies

Did you install the SSU (KB4520724) also?

Have you walked through the online troubleshooter – https://support.microsoft.com/en-us/help/4034932/single-sign-on-not-working-adfs?

--Joe

1 user thanked author for this post.

woody

Reply | Quote

Hi Joe,

Thanks for taking the time to reply.

Yes, the SSU KB4520724 was installed back in December.

I’ll run through the troubleshooter and see if this raises any clues.

Thanks,

Keith

1 user thanked author for this post.

woody

Reply | Quote