Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Certified Platform Identity and Access Management Architect (Plat-Arch-203) Exam - Topic 5 Question 53 Discussion

Posted by Margurite on Oct 19, 2024 at 04:57 PM

A service provider (SP) supports both Security Assertion Markup Language (SAML) and OpenID Connect (OIDC).

When integrating this SP with Salesforce, which use case is the determining factor when choosing OIDC or SAML?

Suggested Answer: B

Get Premium Salesforce Certified Platform Identity and Access Management Architect (Plat-Arch-203) Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test
34 comments · newest first
AD
Adolph 11 months ago
OIDC is more modern, but SAML has its strengths too.
EL
Elly 11 months ago
Definitely need to avoid that login prompt if already signed in!
CH
Cherilyn 12 months ago
Wait, are they really equivalent? That sounds off.
TO
Tori 12 months ago
I think SAML is still pretty secure though.
ES
Esteban 1 year ago
OIDC is better for API calls, right?
HI
Hildegarde 1 year ago
I thought they were similar, but I guess there are specific use cases that might make one better than the other, especially with Salesforce integration.
NA
Natalya 1 year ago
I feel like SAML is more traditional for single sign-on, but I can't recall if that makes it better than OIDC in this scenario.
AH
Ahmed 1 year ago
I think I read somewhere that if the user is already logged into Salesforce, we want a seamless experience, so maybe that's why we would choose OIDC?
DO
Dorothy 1 year ago
I remember discussing that OIDC is often preferred for API calls, but I'm not sure if that's the only factor.
ER
Erinn 1 year ago
If the user already has a session on Salesforce, we don't want to prompt them for credentials again. That's an important consideration.
MI
Micah 1 year ago
The key here is the need for the SP to perform API calls back to Salesforce on behalf of the user. That's the determining factor.
WI
Wilbert 1 year ago
OIDC is more secure, so that seems like the obvious choice. But I'll need to double-check the details to be sure.
CH
Chu 1 year ago
Okay, let's see. The question is asking about integrating with Salesforce, so I'll need to consider the specific requirements there.
MA
Margurite 1 year ago
Hmm, this is a tricky one. I'll need to think carefully about the use case and the differences between OIDC and SAML.
ES
Estrella 1 year ago
OIDC is the 'new kid on the block,' but SAML has been around longer. It's like choosing between the latest smartphone or a classic car - both have their merits.
RI
Richelle 1 year ago
↳ replying to Estrella
A: B) The SP needs to perform API calls back to Salesforce on behalf of the user after the user logs in to the service provider.
KA
Karan 1 year ago
↳ replying to Estrella
B: C) If the user has a session on Salesforce, you do not want them to be prompted for a username and password when they login to the SP.
GI
Gilberto 1 year ago
↳ replying to Estrella
A: B) The SP needs to perform API calls back to Salesforce on behalf of the user after the user logs in to the service provider.
IR
Irving 2 years ago
I'm just glad I don't have to remember all these acronyms on a daily basis. I'll stick to the coffee and let the IT folks handle the technical stuff.
TH
Theron 2 years ago
I disagree with option D. There are significant differences between OIDC and SAML, and the choice should be based on the specific requirements of the integration.
AL
Alpha 1 year ago
↳ replying to Theron
User 3: Option D is not accurate, there are definitely differences between OIDC and SAML that should be taken into account.
CI
Ciara 1 year ago
↳ replying to Theron
User 2: I agree, the SP needing to perform API calls back to Salesforce after the user logs in is a key consideration.
RO
Rosalind 1 year ago
↳ replying to Theron
User 1: I think option B is the determining factor when choosing OIDC or SAML.
PA
Paris 2 years ago
Option C is also important to consider. If the user is already logged in to Salesforce, you want a seamless login experience with the service provider.
DE
Delisa 1 year ago
↳ replying to Paris
A: Exactly, no one wants to keep entering their credentials multiple times.
SO
Socorro 1 year ago
↳ replying to Paris
B: I agree, it's all about making it easy for the user.
AR
Arthur 1 year ago
↳ replying to Paris
A: Option C is definitely important to consider. Seamless login experience is key.
WI
Wilda 2 years ago
OIDC is not necessarily more secure than SAML. The choice depends on the specific use case, as the question states. Option B seems to be the most relevant factor here.
GU
Gussie 1 year ago
↳ replying to Wilda
C) If the user has a session on Salesforce, you do not want them to be prompted for a username and password when they login to the SP.
HO
Hoa 1 year ago
↳ replying to Wilda
B) The SP needs to perform API calls back to Salesforce on behalf of the user after the user logs in to the service provider.
NG
Nguyet 1 year ago
↳ replying to Wilda
A) OIDC is more secure than SAML and therefore is the obvious choice.
KA
Kati 2 years ago
But what about the user session on Salesforce? Wouldn't we want to avoid prompting them for username and password?
KA
Kanisha 2 years ago
I agree with Deonna. If that's the case, then OIDC would be the better choice.
DE
Deonna 2 years ago
I think the determining factor should be if the SP needs to perform API calls back to Salesforce.
0/2000 characters

Save Cancel