MENU
Universal Containers (UC) is building an integration between Salesforce and a legacy web applications using the canvas framework. The security for UC has determined that a signed request from Salesforce is not an adequate authentication solution for the Third-Party app. Which two options should the Architect consider for authenticating the third-party app using the canvas framework? Choose 2 Answers
Suggested Answer: D
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
37 comments · newest first
NI
Nickolas
12 months ago
Why not just stick with the signed request? Feels simpler!
HA
Hana
12 months ago
B is also a good pick, but I prefer A for security.
RY
Ryan
12 months ago
Wait, can OAuth really handle this? Seems risky.
BR
Brittni
1 year ago
Totally agree, SAML is a strong choice!
WI
Winifred
1 year ago
A and C seem like solid options for authentication.
BA
Barney
1 year ago
I vaguely recall something about using Apex classes for registration handlers, but I'm not confident if that's the right approach for this integration.
CL
Clay
1 year ago
I feel like the Authorization Providers could be relevant here, especially since they let external apps authenticate against Salesforce.
SH
Shonda
1 year ago
I think the Canvas OAuth flow might be a good option since it allows for secure authentication, but I need to double-check how it works with third-party apps.
JE
Jerilyn
1 year ago
I remember studying about SAML and how it can be used for single sign-on, but I'm not entirely sure if it's the best fit for this scenario.
TR
Truman
1 year ago
Good point. I think I'll go with a combination of options A and C to cover all the bases.
FR
Francisca
1 year ago
I'm not so sure, I remember something about redundancy, but I can't recall if that meant two links or just one.
VE
Veda
1 year ago
I think I remember that dbowner might be too much for regular access. Maybe datareader and datawriter are better?
PA
Paris
1 year ago
Okay, I think I've got it. Control information directly controls an elementary process, while influence information just affects it. I'll go with option C.
LE
Leonor
1 year ago
Hmm, I'm not totally sure about the service-orientation principles and how they relate to the service contract. I'll have to think this through carefully.
JI
Jin
1 year ago
I hear the security team is also considering a good old-fashioned handshake as an authentication method. You know, for that personal touch.
NI
Niesha
1 year ago
C) Utilize Canvas OAuth flow to allow the third-party application to authenticate itself against Salesforce as the Idp.
SC
Scarlet
1 year ago
That handshake idea sounds interesting, but I think we should stick to more secure options.
CH
Chuck
1 year ago
B) Utilize Authorization Providers to allow the third-party application to authenticate itself against Salesforce as the Idp.
GI
Gilma
1 year ago
A) Utilize the SAML Single Sign-on flow to allow the third-party to authenticate itself against UC's IdP.
LE
Lezlie
1 year ago
Maybe we should just tell the third-party app to use the 'password123' login credentials. That's secure, right?
MA
Major
1 year ago
Creating a registration handler Apex class could also be a good solution for authentication.
SH
Sharen
1 year ago
Another option could be utilizing Authorization Providers for authentication.
VE
Venita
1 year ago
We should consider utilizing the SAML Single Sign-on flow for authentication.
BE
Becky
1 year ago
No, using 'password123' as login credentials is not secure.
TA
Tawny
1 year ago
B) Utilize Authorization Providers to allow the third-party appliction to authenticate itself against Salesforce as the Idp.
TR
Tresa
1 year ago
A) Utilize the SAML Single Sign-on flow to allow the third-party to authenticate itself against UC's IdP.
FA
Fabiola
2 years ago
Wait, so we can't just use a signed request from Salesforce? That's like the easiest option! What's the point of having all these fancy authentication methods if a simple signed request won't work?
PA
Pauline
2 years ago
Creating a registration handler Apex class? Sounds like a lot of custom code just to authenticate the app. I'd rather go with a more standard solution like SAML or OAuth.
EL
Ellen
1 year ago
B) Utilize Authorization Providers to allow the third-party appliction to authenticate itself against Salesforce as the Idp.
DE
Delfina
1 year ago
A) Utilize the SAML Single Sign-on flow to allow the third-party to authenticate itself against UC's IdP.
CA
Catalina
2 years ago
I'm not sure about option C and D. They might not provide the level of security needed for the integration.
JA
Janessa
2 years ago
I agree with Providencia. Using SAML Single Sign-on and Authorization Providers seems like a secure way to authenticate.
CY
Cyndy
2 years ago
I think the Canvas OAuth flow is the way to go. It allows the third-party app to authenticate directly with Salesforce, which seems more straightforward than going through UC's IdP.
PR
Providencia
2 years ago
I think option A and B could work for authenticating the third-party app.
HE
Herminia
2 years ago
The SAML Single Sign-on flow seems like the most secure option to authenticate the third-party app against UC's IdP. This ensures that the app is validated before accessing Salesforce.
NO
Nohemi
1 year ago
B) Utilize Authorization Providers to allow the third-party application to authenticate itself against Salesforce as the Idp.
DO
Donte
2 years ago
A) Utilize the SAML Single Sign-on flow to allow the third-party to authenticate itself against UC's IdP.