wif - Enrich Azure ACS security tokens -



wif - Enrich Azure ACS security tokens -

we considering acs our federated sts. can configure our own custom sts ip-sts, "built-in" identity providers such facebook, live , google. claims rather "poor". claims transformation in acs helps in simple scenario's. looking best-practice handle situation of "missing claims". think need place "decorating sts" in front end of acs. when acs comes security token, decorator can "enrich" security token additional claims. if claims missing, can set user interface inquire user (once) finish profile. way, regardless of user comes from, have claims application requires. thought ? "best practice" in case ? (acs doesn't seem allow programmatic extensions.)

i think reply depend on exact scenario. acs not meant manage profiles , such can, , should do, regards outgoing claims limited more or less design - man-in-the-middle in all-but-one cases.

apart when managing service identities, can work on input receives identity provider , not have remit of managing user profiles or similar.

with in mind think have 2 reasonable options - either identity provide provides more information, can passes through, , potentially transformed by, acs or application receives basic identity ips through acs , manages extended profiles.

i've written latter here

azure wif acs

Comments

Popular posts from this blog

javascript - mongodb won't find my schema method in nested container -

Hibernate criteria by a list of natural ids -

ios - Lagging ScrollView with UIWebview inside -