GeoBliki's Blog

Securing transactional RESTFul OGC Web Services is a challenge but can be done using a hybrid OpenID/OAuth protocol (see OGC OWS-6 interoperability demonstration).

To increase the security assurance level beyond level-1, you need to use more than one authentication factor such as: something you know (password) and something you have (keyfob).  Our openid server is currently being upgraded to support Verisign Identity Protection (VIP) and VIP Access using Mobile Credentials (free for end-users).

If you register a credential in your profile, a security code can now be used in addition to a password to gain access to the SensorWeb services.  A security code can also be used to delegate user authority to consumer applications such as workflows to access services on your behalf.  Credentials will become mandatory to gain access to satellites and UAV tasking request over the web.  There will still be an air gap between users and assets but, at least, user identity will be known with very high confidence.

Our goal is to demonstrate that it can be done simply, cheaply and RESTfully.

Leveraging another Google feat with the newly minted PubSubHubBub protocol or PSHB, interested users can now get real-time notifications when new products from EO-1 are available.  Rather than polling our server at: http://geobpms.geobliki.com/products.atom, consumers can subscribe for that feed at: http://pubsubhubbub.appspot.com/subscribe.

They can enter their own callback to receive changes as it happens.

This capability is also now built-in Feedburner, Google Alerts and Google Reader.  More on TechCrunch

The same feed is available on FeedBurner: http://feeds.feedburner.com/Eo-1Level2ProductFeed

But why would you subscribe to it there?  unless you are a human!

Feel free to use Google Reader and add that feed to your favorites.

Pat.

With the OGC TC in Boston this week, the pressure was up to make those movies available.

The first one is related to RESTFul workflows:

The second one provides more information on the underlying security archtecture:

For SensorWeb to be relevant, we believe that any of its data and assets can be no further away than two degress of separation from anyone in the world. This does assume that those users would be from trusted domains and would have been granted the proper permissions from their organizations.  We are coining this our SWE "Bacon" number or Two.  So, you are doing SWE?  What is your Bacon number?

St Louis, Mar 28, 2008

Just completed a full week of OGC meetings in St Louis. This is the conclusion of OWS-5 (OGC Web Services Interoperability Demo #5) with more than 30 participants.

The NASA SensorWeb is deeply involved in Earth Observation, Natural Resources & Environment. We presented our current ROA-based architecture used to support many pilots and operational demonstrations.

Flip through the presentation on Slideshare and

Watch the first 7mn video here

or this one here as a more technical oriented version (10mn .mov)

| View | Upload your own