This post was most recently updated on December 27th, 2018.Reading Time: 2 minutes.
I stumbled upon a customer, that complained about some pages in their intranet throwing weird errors with authentication. Those pages seemed to have one thing in common – there was a Yammer embed (or a SharePoint script webpart with Yammer embed script in it, to be precise) there. The error code they got was “AADSTS90013: Invalid input received from the user”.
Below, you can see an example of the error screen.
Okay – this is going to be extremely specific, and probably won’t solve the issue for all of you out there! But this is what worked for this customer:
Solution: Check Yammer embed for issues in authentication configuration
In this case, there was a Yammer embed on the page that threw the error. If you’d use a tool like Wireshark (or Chrome network tab and had quick fingers), you’d see that the authentication call to Yammer failed. Hence you’re redirected to login page, which tries to authenticate you against Yammer – and fails. Quite catastrophically, even, and doesn’t return you to the original site.
Now, this should be a fairly fast detour for the user – the login page should actually log you in and then redirect you back! But alas, it fails. Why?
In this particular case, the Yammer embed script was misconfigured. There were extra < > -letters in the network name, and that messed up the authentication. However, the same code had worked just fine for months – even though the embed had those extra letters!
What was wrong with the embed in this case?
So whereas it should’ve been something like this:
It was like this:
(Yammer embed options omitted for clarity)
So, even with the “network” attribute containing a faulty value, it used to work for quite some time. Suddenly, it stopped working.
The embed script itself was probably broken all along. The main thing for us was that everything started working after the embed script was fixed! :)
- How to fix “System.IO.FileSystem: Could not find a part of the path \AppData\Local\AzureFunctionsTools\Releases\3.17.0\workers. Value cannot be null. (Parameter ‘provider’)” when running Azure Functions locally? - January 12, 2021
- How to nuke the Identity Cache in Visual Studio? - January 11, 2021
- Fixing unexpected Microsoft.AspNetCore package errors after a dependency update - January 6, 2021