Identity Provider (IdP): This is the entity providing the user's context and also the one that is capable of authenticating a user.Service Provider (SP): This is the entity providing the service or a web application.Here is an overview of some of the components you’ll encounter: After verifying the SAML assertion, users are granted access to the application. When Freshworks sends requests to an IdP to authenticate a user, the browser is redirected to Freshworks with a SAML assertion. In other words, it is a standard protocol that gives identity providers (IdP) a secure way to let a service provider (SP) like Freshworks know whether you are you. As part of the configuration, Service Provider trusts Identity Provider to verify the user's authentication, and the Identity Provider exchanges this user's identity via a digitally signed authentication assertion with the Service Provider to enable seamless authentication of a user. SAML is a commonly used XML-based authentication and authorization framework to securely exchange information between a Service Provider (example - Freshworks) and an Identity Provider (example - ADFS). Agent SSO and Contact SSO for an Organization.Terms and definitions to understand SSO better.How is the authentication data securely exchanged between IdP and SP.Implement Single Sign-On for Freshworks.
To learn more about SSO, refer to these articles below. You can use Single sign-on (SSO) to log into your Freshworks account via existing SAML-enabled ID providers, such as Active Directory, OneLogin, Okta, etc.
Configuration service provider how to#
Solution home Authentication and Security Single Sign-On (SSO) How to Configure SSO with a SAML 2.0 Identity Provider?
0 kommentar(er)
