We are pleased to announce that we are releasing version 1.0.5 – the newest of our biweekly releases. It has new features and bug fixes, here are the highlights. You can get JayData 1.0.5 from http://jaydata.org/download or from http://jaydata.codeplex.com/releases/view/89056
Sencha Touch 2 UI library support – Read-only scenarios
EntityContext now accepts credentials
password: "password" })
OData provider supports authentication
As authentication happens on a http level, the $data.ODataProvider did support challenge based authentication types (NTLM, Basic, etc) from the beginning. This however involves the browser authentication window to pop up if credentials are missing. OData provider now supports sending Basic authentication headers without a challenge (if credentials are specified when instantiating the context) allowing for custom login screen scenarios.
It’s worth noting that Microsoft LightSwitch supports either Windows(NTLM) or Forms(which is in turn translated to Basic) authentication. Now you can build internet facing LightSwitch apps that use JayData on the client and have your own way of logging people in.
We also created a simple ASP.NET role provider based Basic authenticator ASP.NET module that you can extend with your WCF Data Services based solution.
Attention: Basic authentication is a safe way to do authentication if used with HTTPS!
JaySvcUtil.exe supports authenticated services
JaySvcUtil.exe has now three new command line parameters that let you access an OData endpoint that requires credentials. If not specifying any credentials JaySvcUtil uses the default credential cache, so on an intranet you should not need to specify any account info if you have otherwise access to a service.
-u, --userName: The username to authenticate with
-p, --password: The account password
-d, --domain: The login domain (for NTLM/Window auth)
JaySvcUtil.exe supports V1, V2 and V3 OData services
Supported has been added to JaySvcUtil.exe to recognize multiple OData service versions. The detection is automatic, but you can override it by specifying the –v, –protocolVersion command line parameter.
If used in a Windows 8 / Metro style app, JayData now uses the WinJS.xhr façade method to invoke HTTP calls, also jQuery coupling has been altogether removed, so you can use JayData without including jQuery. The latest release of jQuery does not work in Windows 8 Metro style apps. WinJS.xhr support is not the part of the JayData 1.0.5 standard package, you can get it individually with downloading this JayData Metro app project folder from CodePlex
Check out the release notes for the list of fixes in this release.