azure - When not to use ACS? -


i've been researching azure access control service (acs), , looks it's @ handling authentication heterogeneous (configurable) identity providers. there number of additional scenarios appears support (see example acs how-to's).

the question have opposite: me understand, in order use properly, acs not for. limitations of acs, and/or scenarios acs inappropriate?

(assume, sake of argument, plan create - profitable :) - public web api , corresponding web site front-end, hosted in azure - i.e., care user identity. if like, can further assume system built using .net.)

thanks!

you shouldn't use acs identity provider.

occasionally see confusion role acs serves. acs @ core federation provider, there valid scenario in want backend service (a trusted subsystem) authenticating directly acs using shared secret or certificate. can done using service identities. however, more once i've seen acs scenarios proposed multiple accounts provisioned, , going achieved creating service identity each user.

that's not how acs designed. if suddently have thousands of users, making acs authoritative source user directory won't scale. acs offers nice rules engine designed normalizing incoming claim types various identity providers, or simple authorization policy such generating role claims.

but acs' capabilities here should not confused powered directory, authentication , authorization solutions such ad , adfs. in short, acs not version of ad/adfs.


Comments

Popular posts from this blog

jquery - Invalid Assignment Left-Hand Side -

java - Play! framework 2.0: How to display multiple image? -

gmail - Is there any documentation for read-only access to the Google Contacts API? -