Rationale

OGC Web Services need to be protected a little better that via Basic Authentication.

Standard OAuth 1.0

If you assume pre-approved transaction, follow the following steps:

For Developers

- Register your consumer application to the Geobliki data provider

- Login to http://eo1.geobliki.com with your userid or openid

- Go to: http://eo1.geobliki.com/oauthp/providers

- Create new consumer entry:

Consumer Name:  test_consumer
Consumer Key:   test
Consumer Secret:    123456

For Users

- Specific user grants that consumer access to specific realm. This allows delegation of access authority to that specific consumer.

- Go to: http://eo1.geobliki.com/oauthp/grants

Create new grant 
Select your consumer (if more than one is available)
Enter realm you grant access to: /geobliki

Great job! You are now ready to test the interface!

Next

Implement the OAuth protocol to add additional information in http authentication headers

Getting EO1 SPS Feasibilities:

POST http://eo1.geobliki.com/sps HTTP/1.1
Connection: close
Accept: */*
Content-Type: application/x-www-form-urlencoded
Authorization: OAuth 
oauth_nonce='jepBicIN22C6VBjF08j5EoEdxdwhj7mkjlvcspI9Kc',
oauth_signature_method='HMAC-SHA1'
oauth_token='http%3A%2F%2Fcappelaere.pip.verisignlabs.com%2F',  
oauth_timestamp='1201797367', 
oauth_consumer_key='test', 
oauth_signature='fE9TF9VqXmetHGNQTTobEBpphzY%3D', 
oauth_version='1.0'
Content-Length: 1405
Host: eo1.geobliki.com

"<GetFeasibility>...</GetFeasibility>"

If you fails to do so

The service will return an error requesting OAuth Authentication

if you have any question, send me an email