This document describes UNINETT UWAP + VOOT, a backend-as-a-service API that provides middleware services as a collaboration infrastructure for distributed group-aware tools. It replaces Foodle's role as an experimental integration center. The API uses OAuth for authentication and supports features like group management, activity streams, app hosting, and plans to improve prototypes for pilots and focus on group integration, activity streams, and federated widgets.

1. UNINETT UWAP + VOOT
Dato

2. UWAP
✤ Backend-as-a-service
✤ An API providing a bunch of «middleware services»
✤ Collaboration infrastructure base layer for integrating distributed
group-aware collaboration tools and other services.
✤ Replacing Foodle’s role of experimental middleware integration
center.
API

3. API is protected with OAuth and
WebSSO
Storage
Management
frontend
OAuth
Provider Feide
Engine
Client mngmnt
API
Clients/
WebApps Apps
robots

4. Client management

5. Groups are added.
Storage
Management
frontend
External
Group
connectors:
engine
FS +
OAuth
Provider Feide
Group Engine
management
Client mngmnt
API
VOOT
Clients/
Dynamic attr groups
WebApps Apps
robots
Ad-hoc groups

6. App Storage with authz engine
Storage
Management
frontend
External
Group
connectors:
engine
FS +
Storage
authz
connector
OAuth
Provider Feide
Group Engine
management
Client mngmnt
API
Clients/
WebApps Apps
robots

7. SOA Gatekeeper
Data owner
API
Storage
Management
frontend
External
Group
connectors:
engine
FS +
OAuth
Provider Feide
Group Engine
management
Client mngmnt
API
Clients/
WebApps Apps
robots

8. SOA Gatekeeper

9. Remote data REST API handlers
Remote
Protected APIs
Storage
Management
frontend
OAuth
OAuth
Provider Feide
Group Client
Engine
management
Client mngmnt
API
Clients/
WebApps Apps
robots

10. Remote data REST API handlers
✤ Handles several parallel Oauth protected APIs
✤ Per user per app persistent token cache
✤ Automatic handling of token refresh and initial OAuth bootstrap

11. Activity streams
Storage
Management Activity
frontend stream
External
Group
connectors:
engine
FS +
OAuth
OAuth
Provider Feide
Group Client
Engine
management
Client mngmnt
API
Clients/ eduFeed
WebApps Apps
robots

12. Activity streams
✤ Third party API
✤ Common information objects: video, message, etc.
✤ Group-bound
✤ Filtering and views
✤ Mobile app, to support notifications etc.
✤ Feature is not mature. Few weeks old.
✤ RSS and iTunesU publisher clients.
✤ Planning integration with several tools
✤ Federated widgets!

15. WebApp «Cloud» Hosting

16. WebApp «Cloud» Hosting

17. WebApp «Cloud» Hosting
Remote Data owner
Protected APIs API
Storage
Management
frontend Activity
stream External
Group
connectors:
engine
FS +
Web
DAV Application
access files OAuth
OAuth
Provider Feide
Group Client
Engine
management
Client mngmnt
Apphosting API
js API
Application
static js code

18. Federated Widgets
✤ We’ll present this later. Stay tuned!

19. Plans forward
✤ Improving the prototype - aim for pilot
✤ Focus on group integrations (in and out)
✤ Focus on activity streams demo show cases
✤ Focus on federated widgets
✤ International collaboration partners. Anyone?