How should we do User Access, Accounting, and Authorization? Implementing via Services with OAuth may allow us to use Bespin Client's (future, end of summer) OAuth plug-in. Implementing via our own Bespin Client plug-in would allow us to use Drupal's API directly.

Admins and ops need to be able give permissions just like any other Drupal Module, but how does the creator (or editor) give permissions to other collaborators? How does it fit in seamlessly with Organic Groups?

Comments

tomdavidson’s picture

tomdavidson commented
Priority: Normal » Critical
tomdavidson’s picture

tomdavidson commented

http://groups.google.com/group/bespin/browse_thread/thread/328ae521d5eaf8f0
> 5. Near future Bespin Server will use OAuth, so the Client with have a
> OAuth plugin?
Unfortunately, that's all speculative right now. Until we really dig in on
the new server, it's hard to say exactly how it will end up working. (Kevin Dangoor).

So I think B4D should have its own Drupal Auth Bespin client plug-in that communicates with Drupal via Services.

tomdavidson’s picture

tomdavidson commented
Status: Active » Closed (won't fix)