250 likes | 262 Views
Users’ Authentication in the VRVS System. David Collados California Institute of Technology. November 20th, 2003. TERENA - Authentication & Authorization. What is VRVS?.
E N D
Users’ Authentication in the VRVS System David Collados California Institute of Technology November 20th, 2003 TERENA - Authentication & Authorization
What is VRVS? • TheVirtual Rooms Videoconferencing System has been developed by Caltech since1995to provide aworld widevideoconferencing service for education and research communities. • VRVS isa realtime distributed systemwhichprovide ascalable communication infrastructurefor large collaboration dispersed all over the world. • Different technologies and protocols are supported(and mixed) and allow users to connect their preferred videoconference. • SupportsMbone, H.323, SIP, QuickTime, Access Grid, JMFandMPEG2. • The system is composed of1 main serverandseveral reflectorsspread around the world.
VRVS Web Service Design • Unified Web User Interfaceto schedule and join/leave a meeting independently of any application. • Multi-platform: Windows, Linux, MacOS and Unix • Easy to use: Everybody knows how to click on a web page today. • Virtual Room Concept, Scheduling: Create a virtual space were people can exchange real-time information • Join or Leavea Collaborative session at anytime. Noneed to know in advance how many participants and booked ports capacity. • FullDocumentation and Tutorial • Self service: No need for a technician or expert to organize and join you into a conference.
VRVS Model Implementation done Partially done Continuously in development Work in progress VRVS Web User Interface Mbone Tools (vic, vat/rat,..) SIP H.323 QuickTime Player MPEG Minerva Collaborative Applications VRVS Reflectors (Unicast/Multicast) QoS Real Time Protocol (RTP/RTCP) Network Layer (TCP/IP)
VRVS Reflectors Deployment 78 Reflectors deployed worlwide
VRVS Reflector Implementation • Avoids Duplicationof Streams on a given Link • Can be set toUnicast or Multicastmode or both • Connectionpeer-to-peerwith neighbors network servers. Connectionless (more reliable to network breaks) • EnablesOptimized Routing • EnablesBandwidth Control • Providelow latency communication • Could be use forreal-time interactivityorbroadcast • Provide elegant solution to crossfirewall/NAT • RemoteManagementFeatures. • Compliant withIETF RTPv2 Protocol, ready for new applications.
Registered users and current usageas of (16th November 2003) Number of Registered Users: 96 Countries & 6615 Users Slovakia, Chile, Poland, Russia, Taiwan, Greece, Netherlands, etc…
Machines and OS • VRVS supports different • Operating Systems based • on the needs and • demands of final users: • 1st : Windows • 2nd: Linux • 3rd: Mac OS • 4th: Other UNIX • 19.461 machines • (16th November 2003)
VRVS on Windows KEK (JP) Caltech (US) RAL (UK) Brazil CERN (CH) AMPATH (US) Pakistan SLAC (US) Canada AMPATH (US)
Example 1: 20 participantsBRAZIL (3 sites) + SWITZERLAND (CERN) + USA (Caltech)
Example 2: 17 participantsJAPAN + UK + SWITZERLAND + BRAZIL + USA (SLAC + FERMILAB)
VRVS Virtual Setup 1 dual processor PC With special 4 outputs graphic card 6400 x 4800 pixels Most powerful VRVS End Node
Authentication and Authorization - Present Status -
Users’ Site (Apache) • Database Authentication module for browsing most of the site. • One single realm for the whole site. • Caching just for the current browser session.
Authorization of Users 1/2 • Each VRVS user belongs to a Community. The responsible/s for that community will authorize (or not) bookings from that user in their community.
Authorization of Users 2/2 • Other mechanism of authorization is implemented when joining a meeting (Virtual Room access protected with password).
Administration Site (Tomcat) • Database Authentication for the whole site. • JDBC Realm implemented for MySQL DB. • Administrators database with MD5 digest algorithm for stored passwords.
Authorization @ Admin Site • Different roles defined in the DB attached to the users. • The Call Detail Record example. Oriented to roles.
Authentication and Authorization - Future -
AA in the VRVS Future • AA independent of our system and distributed. • Internet2 initiative: Shibboleth. • RedIRIS initiative: PAPI. • Grid Security Infrastructure (GSI): public key encryption, X.509 certificates, SSL + extensions for delegation and single sign-on. • What do we integrate and how?
WWW.VRVS.ORG Contact@VRVS.org Support@VRVS.org