Can I Install Sign in SalesForce

How To Integrate Sign in SalesForce

hi the purpose of this video is to show you how to implement single sign-on in Salesforce before we actually get into the implementation I'd like to take a couple of minutes to go through some of the basics of single sign-on and the components involved in a single sign-on deployment so single sign-on is a process that allows the user to access multiple applications or systems after going through the authentication process only once since the else force provides a couple of different ways to implement single sign-on delegated authentication and federated authentication delegated authentication is a proprietary Salesforce solution that captures the user login credentials and sends it over to an external web service for authentication now the external web service has to be developed built and deployed by the client a couple of drawbacks to this option or that it's not as secure it you know when the web service is down user will not be allowed to log in and it can only be configured at a profile level within Salesforce the second option which is the federated authentication is a more widely accepted single sign-on solution because it is based on an industry standard called sam'l sam'l is nothing but security assertion markup language it is based in an XML format and it is the industry standard for federated SSO deployments it's used by Federation partners to share identity attributes of the user there are two versions of sam'l available saml 1.1 and sam'l 2.0 salesforce only supports sam'l 2.0 because that's the latest version in the sam'l scenario there are a couple of actors involved the first is the identity provider and the second is the service provider identity provider is the system that is providing the sam'l assertion which contains the users identity and that's passed over to the service provider the service provider is the system that is consuming the assertion that is passed and from the identity provider it uses the assertion to gather the user attributes and based on that information it allows the user to log in to the requested resource server for the purposes of our implementation we're going to use two Salesforce orgs we're gonna set up the first org as an identity provider and the second org as a service provider so we're gonna test a couple of scenarios when when a user logs into the first identity provider org they should be able to click link which takes them to the second service provider org without having to log in once again and what's what single sign-on there are a couple of different flows and we can test both these flows the first flow is the identity provider initiated flow so with this flow the user logs into the identity provider and after logging in twice to access the service provider when that is done the identity provider sends over a sam'l assertion to Salesforce and the sam'l assertion has details like the Federation ID...