UNINETT IoU - UWAP Prototype

UWAPA Cloud Service Platform.

Andreas Åkre SolbergUNINETT, WebTechnology Research and Development

11. December 2012

Web Single Sign-On with Feide was sufficient to provide

a seamless user experience across services.

Once upon a time

Collaboration on Internet

✤ A dynamic working groups spanning multiple organizations, work together using digital collaboration tools:

✤ A wiki

✤ Document sharing tool

✤ Meeting planner and calendar

✤ A Web meeting tool

✤ A web forum or mailinglist

to provide a satisfying end-user experience spanning multiple collaboration services today,SSO is not sufficient.

Traditional approach

User directory

App1

App2

App3

Batch provisioningof users and groups

✤ Does not scale

✤ Not dynamic

✤ (Often) only in one direction

✤ But it works,for some use cases

Modern services

✤ Modern collaboration services share a bunch of common components:

✤ Users and authentication

✤ Groups and authorization

✤ Invitation (mapping users and groups)

✤ Activity stream

✤ Notifications (mail and mobile push notifications)

✤ Data access with third party REST API

Service Platform Architecture

Service Platform

Feide

App App App App App

Authentication

People search

Calendar sharing

Activity stream

Groups and authorization

REST API Engine

Notifications

Super simpleintegration

UWAP

Service Platform Architecture

Service Platform

Feide

UI UI UI App App

Authentication

People search

Calendar sharing

Activity stream

Groups and authorization

REST API Engine

Notifications

All platform UI built asindepedent apps

App App

UWAP

UWAP

SurfConext

SurfConextSURFfederatie

Ad-hoc Groupmanagement

Service Service

Authentication

Groups and authorization

Service Service

SAML SAML SAML SAML

Facebook

App App

Authentication

Activity stream

Social network / groups

Notifications

Third party apps App App

Focus on individual rather than group

Application

Super simpleintegration

Groups

Service Platform

Ad hoc groupmanagement

Storage

Attributes from Feide FS SurfConext +++

App App App ✤ Dynamic large-scale groups from Feide attributes✤ Organization, department✤ Affiliation: like «all students at NTNU»

✤ Ad-hoc groups✤ Groups from external systems

✤ FS✤ KIND, etc.

Activity streams

Andr

eas c

reate

d a w

iki pa

ge

«welc

ome!»

at A

gora

Armaz

shar

ed a

file «a

rchite

cture

.pdf»

at C

louds

tor

Simon

sch

edule

d a ne

w mee

ting

Andr

eas c

onfirm

ed an

d

will a

ttend

mee

ting

A ne

w us

er Th

orlei

f is

adde

d to t

he gr

oup

› One activity stream per group.› Generic information model› Acitivites posted to one or more groups

Public / PrivateNormal / Promoted

User interfaces› WebApp frontend› Mobile app frontend› Widgets› API

Notifications

✤ The most important activity updates

✤ Email and mobile push notifications

✤ Personal preferences

Invitations, people search

✤ Protected with Feide

✤ Generic js library

✤ Very easy integration in all applications that needs to «add users».

Federated Widgets

✤ Embed content on remote site

✤ Challenge:

✤ secure environment

✤ authentication

Federated Widgets

✤ Super simple integration!

✤ Secure separation from container site

✤ Auto-detecting existing Feide session

✤ No server-side requirements...

Federated Widget

✤ The group-context-aware «webmeeting button»

Webmeeting using

Adobe Connect

Join meeting

Feed WidgetShows an aggregated feed of activities for the current

selected group across all collaboration tools.

Share widgetCan be easily integrated anywhere. Will share a link to the current web page

to the activity stream for the current user in a selected group context.

Feed WidgetShows an aggregated feed of activities for the current

selected group across all collaboration tools.

RedMineWith Activity Stream Connector enabled.

WebApp Hosting

creating a new application...

How does it work

✤ Each app gets their own domain: myapp.eduapps.org

✤ App engine provides a javascript API to access all functionality

✤ The javascript engine communicates with app server using REST api.

✤ Let’s test it...

89 lines of code (mostly UI)

...some of the apps developed by summer student Terje Navjord making use of the UWAP platform.

How to present all these cool applications to potential end users?

App store.

App Store

Connecting edu institutions to content providers with new more efficient and fair payment models

Authorization data

New Potentials

SOA Gatekeeper

✤ Manage 3rd party clients

✤ Control your open APIs

✤ User control, scopes, consent etc.

Thanks.