Name: SAML: Identifying Common Missteps in SAP Customer Data Cloud
Uploaded: 2019-8-19
Duration: 196 s
Description: This video is a part of the series of videos which covers the SAML topic in detail. This video covers common missteps while setting up SAML in CDC.Watch the following video to know about SAML and IDP Configuration.Introduction to SAML and IdP Configuration - SAP Customer Data Cloud

Share feedback

<p><u><strong>Planned maintenance of Practice Systems</strong></u></p>

Planned maintenance of Practice Systems

Why create an SAP account?

Enhance your learning experience

SAP Learning

Choose your subscription

Manage your subscription

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

<div><div><div><div><div><div><div><div><div><div><div><div>This video is a part of the series of videos which covers the SAML topic in detail. This video covers common missteps while setting up SAML in CDC.<br><br>Watch the following video to know about SAML and IDP Configuration.<br><a href="https://learning.sap.com/videos/introduction-to-saml-and-idp-configuration-sap-customer-data-cloud" rel="nofollow noopener noreferrer" target="_blank">Introduction to SAML and IdP Configuration - SAP Customer Data Cloud</a></div></div></div></div></div></div></div></div></div></div></div></div>

SAML: Identifying Common Missteps in SAP Customer Data Cloud

In this video, we will cover some common issues that clients struggle with. Of course, there are several ways to configure a connection. We have seen quite a few, but these ones keep coming up. Oftentimes you may have the wrong issuer ID or entity ID. The issuer ID might not be a URL. You may have an incorrectly formed proxy page, or you might be calling init SSL or continuing SSL in the wrong scenario. One thing to watch out for is the issuer ID. Most clients are not familiar with how to properly find the values for this field. So they may give you best guesses or complete hogwash. However, the correct data is sent by the service provider during a simple request. So assuming that they have plugged in the IDP settings in the right places on their hand, you can find the correct configuration by debugging a connection. We will see how to find the service provider data from the SAML request data in a moment. And when we do, we can easily verify the issuer ID and other settings. Also related to the issuer ID is that the SAML specification declares that it must be a URL. Not all thermal implementations enforce this restriction. So if you see an issuer idea that is not a URL, that should be a red flag because it can't be fixed by making a change on the site. Another common pitfall is an incorrectly formed proxy page. Clients don't always understand the purpose of the proxy page, so they set the value to their main login pages. As we saw in the first video, in this serious, the proxy page needs only to contain a single script tag with three important URLs and no actual content. This one can be tricky because the content of the page does not appear in the network panel on most browsers, because the page immediately redirects. However, if you load the page source manually, you can confirm its contents. Keep in mind that this page is loading a special SAML JavaScript library, which is what lends the proxy page all of its power to its lack of content. Fooled you into forgetting how important its role in the SAML process. It's easy to confuse the continued SSL, and in it SSL calls in the JavaScript SDK, though they both service part of different floats, each of them are called by the identity provider or in its SSL is called at the beginning of the identity provider initiated flow. When a logged in user clicks on the link to an ISP provided resource continuance, SSL is called at the end of an ISP initiated flow immediately after the user finishes logging in. That ends the common issues which are frequently encountered in the SAML implementation. Thanks for watching.