salesforce - Salesforce 中的联合身份验证和委托(delegate)身份验证

Question

有人知道 Salesforce 中联合身份验证和委托(delegate)身份验证之间的区别吗？你能解释一下这两种方法中请求的流程吗？

Answer 1

主要区别是在联合身份验证中使用安全断言标记语言 (SAML)。

Delegated Authentication Use delegated authentication if you have mobile users in your organization, or if you want to enable single-sign on for partner portals or Customer Portals. You must request that this feature be enabled by salesforce.com. This recipe explains delegated authentication in more detail.

Federated Authentication using SAML Federated authentication uses SAML, an industry standard for secure integrations. Investing in SAML with Salesforce.com can be leveraged with other products or services. If you use SAML, you don't have to expose an internal server to the Internet: the secure integration is done using the browser. In addition, Salesforce.com never handles any passwords used by your organization. For more information, see “Configuring SAML Settings for Single Sign-On” in the Salesforce.com online help.

差异

委托(delegate)身份验证相对于联合身份验证有一些缺点。一、 委托(delegate)身份验证本质上是**不安全的比联合身份验证**。即使加密，委托(delegate)身份验证仍会通过 Internet 将用户名和密码(甚至可能是您的网络密码)发送到 Force.com。一些公司的政策禁止第三方处理其网络密码。二、 委托(delegate)身份验证**需要更多工作对于实现它的公司**。为组织配置的 Web 服务端点必须经过开发、托管、在 Internet 上公开并与公司的身份存储集成。

delegated 上更详细的流程和代码示例



更多详细流程请访问 SSO width SAML