What can be done in case the SIngle Sign-On gateway Url is invalid?
I have used Single Sign On through ADFS as the identity provider. It was tested in sandbox, and in production before release. In release, there are few users who can login through SSO, and others use the same instructions but are not able to login. Successful users login type is SAML SFDC initiated SSO. Failed login trials display Application as the login type, and see the error message:
‘The SIngle Sign-On Gateway Url is Invalid’. Which setting in Salesforce identifies the login type and gateway url? How to fix the problem?
Majority of the users could login successfully but few got the error message. The case sensitivity of the user lookup was the problem. We are utilizing ADFS that returns the mail address of the user after proper verification that looks up the user’s salesforce account through the federation id. The ambiguous thing was the mail id in AD that looked good but on keen inspection, we found that the O365 account was not syncing.
Navigating to Setup > Single Sign-On Settings you'll find a setting labelled'Make Federation ID case insensitive'.
On activating the setting, the users could properly sign in. You can check if this is the problem by choosing the button SAML assertion validator on the SIngle Sign On settings page.
TheSalesforce Certification Training offered at JanBask Training provides experience like offline classes to help candidates master the Salesforce Development and Administration in a better way to face the tough job market scenario. The course guarantees job success and lets you qualify the certification exam through intensive, and expert-led virtual sessions and hands-on practical assignments. The course will teach you to create and configure the salesforce account to help you gather, extract, and examine the data relevant to the customer base. You can also avail the Force.com platform to create and use the advanced cloud apps with utmost confidence.