Talk:Atomic authorization

This article has not yet been rated on Wikipedia's content assessment scale. It is of interest to the following WikiProjects:

Computing This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles ??? This article has not yet received a rating on the project's importance scale. Science This article is within the scope of WikiProject Science, a collaborative effort to improve the coverage of Science on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ScienceWikipedia:WikiProject ScienceTemplate:WikiProject Sciencescience articles ??? This article has not yet received a rating on the project's importance scale.

This article seems too thin. I would like to know how is this different from federated identity and saml assertions? How does this compare to what XOTA does and other extended universal authentication systems? Should sections be added about this? Does atomic authorization supersede other types of authorization?

Is there an atomic form of authentication that coincides with atomic auth?

I think that a classic Bob, Eve and Alice scenario showing atomic authorization in an example would help (me, at least). Shurdloo (talk) 17:57, 15 July 2010 (UTC)[reply]

I understand that atomic authorization implementations are done to prevent a single compromise from changing authorizations across multiple users, but I don't think that comes out in this article. It would also help to point out that SAML and XACML on the surface do not provide atomic authorization until the token itself is signed. Then the authorization can be atomic. On the back end database it is only an atomic authorization if a database compromise offers the attacker no ability to manipulate the authorization beyond removing it (failing closed). These would be helpful to graft into the description. —Preceding unsigned comment added by 71.246.246.44 (talk) 01:45, 16 July 2010 (UTC)[reply]