learning from reso odata and oauth – and onto documentdb’s security model

it was fun to see how NAR politics has manipulated the RESO process, in both the odata and oauth spaces. But we can move on, since there is no more R&D to be done in the area for now.

Now, what we did learn was all about node.js, mongodb and the apparatus that goes with it. We can start to look into the windows worlds equivalent (documentdb) and see what a “pure” json-centric webapi server looks like – when constructed using azure cloud principles and microsoft libraries.

in particular, we need to see just how folks have orchestrated how an azure mobile site really works with a documentdb collection and the db account, in terms of identity, identity pass through, 3tier systems, and the like.

In the NAR node.js prototype, we saw how the webapi server expected to work with mongodb accounts. Inb the azure mobile with sql and odata/table stores, we saw how the schema or the masterpartition key was used to segment the spaces by either app or by user (within the app).  With documentdb, lets hope we have a much better though through model – in the sense that it all cues off tokens, token handoffs, and claims, etc.

Before we go there, lets go have a looksie and modern joomla hosting in azure websites and Amazon EC2 web services (and its security model). It will be interesting to compare azure and amazon, and see how much commonality there is around upper layers security.


About home_pw

Computer Programmer who often does network administration with focus on security servers. Sometimes plays at slot machine programming.
This entry was posted in coding theory. Bookmark the permalink.