Check the ADFS logs to find the cause of a failed SAML sign-in to Robin. To set up SAML with ADFS first, see Enabling single sign-on via ADFS.
When a SAML sign-in fails, Robin shows as much information as it can in the error message. How much it can show depends on what your ADFS server sends back. The ADFS server has the most detail, so use its logs to troubleshoot.
Open the Event Viewer
The screenshots show Exchange Server 2013. The steps should be similar for versions 2010 and higher.
The logs are usually on the ADFS server, in the Event Viewer application. Sign in to your ADFS server and go to Control Panel > Administrative Tools > Event Viewer. If you do not see Administrative Tools, change the view to "Small Icons".
Find SAML error messages
The Event Viewer shows a folder tree on the left with the applications on your server. Select Application and Services Logs > AD FS > Admin. Your server can label these folders differently, but they should hold the same information.
A busy server can log thousands of entries each day. To narrow them down, use the Find menu item on the right. Search for keywords such as "SAML" or "robinpowered.com", which matches Robin's SAML entity ID. The most recent sign-in attempts are at the top of the page.
Select an Error log entry to see more about the issue. The example below shows details about an Invalid NameIDPolicy, and which one your server expected for the service's Relaying Trust Policy.
With these logs, you should be able to troubleshoot specific issues faster, without trying different SAML configurations by trial and error.