New answers tagged

2

I think the second problem you listed is causing the first problem, and unfortunately it's a bit of a layered answer. I'm also assuming that the MetadataService layer you've generated is all correct. The first part to solve is getting the ConnectedAppOauthConfig.isAdminApproved = true. Now I couldn't get this to set on creation of the Connected App. However,...


0

All that means is that your Identity Provider is responsible for generating the SAML Response (also called the SAML assertion). To use the SAML or SAML Bearer Oauth flows you must have an external Identity Provider that has been configured for SSO in Salesforce. Commonly, this would be the same identity provider that users use when they SSO in. Some ...


0

Salesforce supports two SAML-for-oAuth flows: one standardized in RFC 7522 and the other a very similar but proprietary to SF flavor thereof. The first flow is referred to as oAuth 2.0 SAML 2.0 Bearer Assertion by SF docs, second one is simply "SAML Assertion Flow": In either flow, obtaining a SAML assertion and making sure that it has the right content is ...


0

Well, SAML is a way to facilitate Single Sign-On (SSO). Using SSO means you should have an external SAML Service Provider that can take a SAML assertion and get the response you need. It's hard to tell you exactly what you need to do here, because that will depend on the specifics of the Service Provider your organization is using. It comes down to "you ...


2

Taking the summary out of comments for everyone's benefit: the screens you reference are for implementation of a scenario where an external service/app is acting as a SAML identity provider, SF is a service provider. SamlSsoConfig is the metadata object that corresponds to the Single Sign-On Settings screen, it captures a configuration of the (external) ...


Top 50 recent answers are included