CloudServices/Roadmaps/Server: Difference between revisions

CloudServices/Roadmaps/Server (view source)

411 bytes removed , 25 July 2011

canmove, Confirmed users

1,173

edits

@@ Line 59: / Line 59: @@
 === Auth ===
-Technically, this is part of user management. However, it's worth calling out separately, because it is the user management piece that all our products tend to use. Should we tear it out into its own space to make it easier to extend?
+Technically, this is part of user management. However, it's worth calling out separately, because it is the user management piece that all our products tend to use.
-The usual profile of a user interaction with the Sync server is to request info/collections, followed sometimes by a series of futher requests. Each request does a pair of LDAP calls (one to get the DN, one to bind). Can we do some sort of short-term caching that will let us only talk to LDAP once for each of these 'sessions'? How do we handle password changes? Can we abstract this out to something more generic?
+Auth eventually needs to encapsulate a permissions model. This can be done through a token based permissions system that is generated once logged in. We'll use whatever the favored identification system to come out of browserID.
-Auth needs to encapsulate a permissions model. This can be done through a token based permissions system that is generated once logged in. We
+Bugs:
-ll use whatever the favored identification system to come out of browserID.
+* Cache authentication credentials for a period of time
 === Test Support ===