You need to allow users to access the application by using their Google accounts

You administer an Access Control Service namespace named contosoACS that is used by
a web application. ContosoACS currently utilizes Microsoft and Yahoo accounts. Several
users in your organization have Google accounts and would like to access the web
application through ContosoACS.
You need to allow users to access the application by using their Google accounts. What
should you do?

You administer an Access Control Service namespace named contosoACS that is used by
a web application. ContosoACS currently utilizes Microsoft and Yahoo accounts. Several
users in your organization have Google accounts and would like to access the web
application through ContosoACS.
You need to allow users to access the application by using their Google accounts. What
should you do?

A.
Register the application directly with Google.

B.
Edit the existing Microsoft Account identity provider and update the realm to include
Google.

C.
Add a new Google identity provider.

D.
Add a new WS-Federation identity provider and configure the WS-Federation metadata to
point to the Google sign-in URL.

Explanation:
http://msdn.microsoft.com/en-us/library/azure/gg185976.aspx



Leave a Reply 16

Your email address will not be published. Required fields are marked *


joni

joni

what is the correct answer?

CastorTray

CastorTray

I think it’s “C”

Configuring Google as an identity provider eliminates the need to create and manage authentication and identity management mechanism. It helps the end user experience if there are familiar authentication procedures.

Reference: How to: Configure Google as an Identity Provider URL: http://msdn.microsoft.com/en-us/library/azure/gg185976.aspx

joni

joni

I agree its C

Mark van Dijk

Mark van Dijk

Answer C seems valid. Thanks CastorTray.

phone7

phone7

Samji is right:

Google has closet OpenID 2.0 registrations and this feature is deprecated

SCIw7luXRMY

SCIw7luXRMY

49717 147933In the event you happen to significant fortunate individuals forms, referring by natural means, moreover you catch the attention of some sort of envy in consideration of those types the other campers surrounding you which have tough times about this subject. awnings 813246

bursa orospu

bursa orospu

607966 669763hey very good internet site i will definaely come back and see once again. 649952

ankara escort

ankara escort

813100 809516It is a shame you dont have a donate button! Id most undoubtedly donate to this outstanding internet web site! I suppose within the meantime ill be pleased with bookmarking and putting your Rss feed to my Google account. I appear forward to fresh updates and will share this weblog with my Facebook group: ) 615734

company website

company website

103562 253388Aw, it was a genuinely very good post. In concept I ought to put in writing related to this furthermore – spending time and actual effort to manufacture a exceptional article but exactly what do I say I procrastinate alot and no indicates uncover a strategy to go carried out. 568084

cutedevil

cutedevil

Answer is A.Register the application directly with Google.

June 2014 – Google Identity Provider Support

As of May 19, 2014, new ACS namespaces cannot use Google as an identity provider. ACS namespaces that used Google and were registered before May 19, 2014 are unaffected. This new limitation exists because Google is phasing out support for OpenID 2.0, which ACS depends on, and has closed registration for new applications. Existing ACS namespaces that used Google will continue to work until April 20, 2015. If your application requires support for Google accounts, we recommend that you register your application with them directly.
https://msdn.microsoft.com/en-us/library/azure/gg429787.aspx

https://msdn.microsoft.com/en-us/library/azure/gg185976.aspx

Antonello

Antonello

Cutedevil in the same article we can read:
March 2015 – Migrate ACS Namespaces to Google OpenID Connect

ACS has implemented a feature to help ACS namespace owners migrate their Google identity provider configurations from OpenID 2.0 to OpenID Connect. Customers will have until June 1, 2015 to migrate their ACS namespaces to OpenID Connect and until Jan 1, 2017 to migrate their backend code to use OpenID Connect identifiers. Failure to perform the appropriate action before each deadline will cause disruption to your applications. For detailed guidance, see Migrating ACS Namespaces to Google OpenID Connect.

So Add identity provider still valid answer. So C is the correct answer for me.