Changes between Version 7 and Version 8 of T12_Security/ESG/SecuringOPeNDAP


Ignore:
Timestamp:
12/11/09 15:04:29 (10 years ago)
Author:
pjkersha
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • T12_Security/ESG/SecuringOPeNDAP

    v7 v8  
    11[[WikiInclude(T12_Security/_menu)]] 
    22== Security Layer for OPeNDAP Service == 
    3 The Sequence Diagram below shows the series of steps for a HTTP client to access a secured OPeNDAP service.  The User Agent could be a web browser, wget program or other HTTP client.   A scenario is envisaged with a BADC Data Node hosting an OPeNDAP service.  The Data Node has security middleware components which front the OPeNDAP application and intercept requests.  The component architecture is assumed to be Python [http://wsgi.org/wsgi/WSGI] based.  Components in the web application middleware stack communicate with one another using WSGI. 
     3The Sequence Diagram below shows the series of steps for a HTTP client to access a secured OPeNDAP service.  The User Agent could be a web browser, wget program or other HTTP client.   A scenario is envisaged with a BADC Data Node hosting an OPeNDAP service.  The Data Node has security middleware components which front the OPeNDAP application and intercept requests.  The component architecture is assumed to be Python [http://wsgi.org/wsgi/ WSGI] based.  Components in the web application middleware stack communicate with one another using WSGI. 
    44 
    55The User Agent makes a request to the OPeNDAP service.  This is intercepted by the Session Handler.  This checks with the authorisation handler to see if the requested URI is a secured one.  This is the case, so the Session Handler then checks to see if the user has a valid session cookie.  The user does not so they are returned a redirect request to redirect them to the Authentication Handler.