OData Archives | Page 4 of 5

Data Services Streaming Provider Series-Part 2: Accessing a Media Resource Stream from the Client

DB BlogsSeptember 8, 2010Sep 8, 201009/8/10

In this second post in the series on implementing a streaming data provider, we show how to use the WCF Data Services client library to access binary data exposed by an Open Data Protocol (OData) feed, as well as has how to upload binary data to the data service. For more information on the streaming provider, see the first blog post in this ...

OData and Authentication – Part 8 – OAuth WRAP

DB BlogsAugust 19, 2010Aug 19, 201008/19/10

OAuth WRAP is a claims based authentication protocol supported by the AppFabric Access Control (ACS) which is part of Windows Azure. But most importantly it is REST (and thus OData) friendly too. The idea is that you authenticate against an ACS server and acquire a Simple Web Token or SWT – which contains signed claims about identity / ...

Data Services Streaming Provider Series: Implementing a Streaming Provider (Part 1)

DB BlogsAugust 4, 2010Aug 4, 201008/4/10

The Open Data Protocol (OData) enables you to define data feeds that also make binary large object (BLOB) data, such as photos, videos, and documents, available to client applications that consume OData feeds. These BLOBs are not returned within the feed itself (for obvious serialization, memory consumption and performance reasons). Instead, ...

OData and Authentication – Part 7 – Forms Authentication

DB BlogsJuly 21, 2010Jul 21, 201007/21/10

Our goal in this post is to re-use the Forms Authentication already in a website to secure a new Data Service. To bootstrap this we need a website that uses Forms Auth. Turns out the MVC Music Store Sample is perfect for our purposes because: The rest of this post assumes you’ve downloaded and installed the MVC ...

OData and Authentication – Part 6 – Custom Basic Authentication

DB BlogsJuly 21, 2010Jul 21, 201007/21/10

You might remember, from Part 5, that Basic Authentication is built-in to IIS. So why do we need ‘Custom’ Basic Authentication? Well if you are happy using windows users and passwords you don’t. That’s because the built-in Basic Authentication, uses the Basic Authentication protocol, to authenticate against the windows ...

OData and Authentication – Part 5 – Custom HttpModules

DB BlogsJuly 19, 2010Jul 19, 201007/19/10

In the last post we saw how to add custom authentication inside your Data Service using the ProcessingRequest event. Unfortunately that approach means authentication is not integrated or shared with the rest of your website. Which means for all but the simplest scenarios a better approach is needed: HttpModules. HttpModules can do all sort of ...

OData and Authentication – Part 4 – Server Side Hooks

DB BlogsJuly 19, 2010Jul 19, 201007/19/10

If you secure an OData Service using Windows authentication – see Part 2 to learn how – everything works as expected out of the box. What however if you need a different authentication scheme? Well the answer as always depends upon your scenario. Broadly speaking what you need to do depends upon how your Data Service is hosted. ...

Join the OData Mailing List

DB BlogsJune 28, 2010Jun 28, 201006/28/10

Today we released an OData Mailing List. This is the list to use if you have OData questions, comments on OData or want to discuss how OData should evolve over time. To sign up to the list go here and follow the instructions provided. The list is fully open so anyone can subscribe and participate. Be sure to read the ...

OData and Authentication – Part 3 – ClientSide Hooks

DB BlogsMay 24, 2010May 24, 201005/24/10

So far in this series we’ve looked at Windows Authentication. For both Windows and Basic Authentication, Data Services does the authentication handshake and subsequent sending of authentication headers – all without you directly setting a http header. It can do this because there is a higher level abstraction – the ...

Using Restricted Characters in Data Service Keys

DB BlogsMay 21, 2010May 21, 201005/21/10

If your Data Service includes entities with a string key, you can run into problems if the keys themselves contain certain restricted characters. For example OData has this uri convention for identifying entities: ~/Feed('key') So if the 'key' contains certain characters it can confuse Uri parsing and processing. Thankfully though Peter Qian...

OData

OData Archives | Page 4 of 5 | OData