Chris Risner . Com

Version 1 of the Mobile Services JWT token has been deprecated

Posted on: 4/22/2014 6:39:00 PM by

If you’ve been using Azure Mobile Services lately, you may have noticed a warning appearing in your logs with the following message:

Version 1 of the Mobile Services JWT token has been deprecated.  Please contact mobileservices@microsoft.com to find out how to update your code.

First, don’t freak out.  There’s a pretty good chance this doesn’t affect you at all.  Due to an unfortunate misstep, this warning has been showing up for some people that aren’t actually affected.  Read on to see if you need to make any changes.

Custom auth

Essentially, you only need to worry about this message if you’re doing custom auth with your Mobile Service.  If you are, you most likely found it in one of these locations:

The reason that you’re affected if you’re doing custom auth is that you’re generating your own JWT tokens.  If you’re using any of the built in auth (Facebook, Google, Microsoft, Twitter) than your Mobile Service generates the JWT for you and your service is already updated.  If you are doing custom auth, read on for the instructions on how to update your code.

Updating the auth code

Thankfully, the changes required to move to version 2 are very simple and they can all be done in the server side scripts.  Here we have the code previously used to specify the contents of the JWT (note I’ve left off the code to make this URL friendly, merge it, etc):

We need to make two alterations to this code.  First the kid value needs to change from an integer to a string, so “0”.  Second, the ver value needs to change to 2.  Our updated code will look like this:

There is one other change you’ll have to make if you’re also doing custom claims.  If you’re specifying a urn:microsoft:credentials as part of the j2 value above, you’ll need to change it to match this shape:

Summary

Version 1 tokens will continue to work for some time though you’ll see that warning pop up in your logs if you continue to issue V1 tokens.  Thankfully the changes are small.  As always, I would advise making your changes against a test service prior to making the changes against a service backing a production app.  You can read more about the changes on the Azure Mobile Services blog.

Categories: Azure, Mobile Services
Bookmark and Share
First Article

Welcome to Microsoft Azure

Posted on: 4/21/2014 4:17:00 PM by

Just about a few weeks ago, we announced that the name of “Windows Azure” would be changing to “Microsoft Azure”.  With Build approaching, I was so busy I didn’t have time to do much more than tweet about the name change.  Now that things have slowed down a bit, I thought it would be a good time to reflect on this change. 

To start, I think it was a great, very logical decision to make.  For many people around the world, I think the words Microsoft and Windows are synonymous.  For a slightly smaller subset (I mean we are talking about billions of people that are familiar with Microsoft and Windows), they’ll know that Windows is something Microsoft makes and that Microsoft is more than just Windows.  Unfortunately, with a name like Windows Azure, it sounds like a version of the Windows operating system.  I’ve literally had people at conferences answer the question “do you know what Windows Azure is?” with “is that a new version of Windows?”  Anyone that’s taken a look at the cloud or done any work with it knows that isn’t the case, but it’s an easy mistake to make.  Having a name like “Windows Azure” ties all of the Azure cloud stuff back to a system people think of as an operating system for computers. 

At one point, this may have made sense.  When Azure first launched it really was a cloud host for .NET applications built on top of Windows Server.  Flash forward to today and Azure is a very very different beast.  IaaS has support for Linux and Oracle (in addition to Windows Server).  Mobile Services has SDKs and walkthroughs for iOS and Android apps.  Azure Web Sites now has support for Java apps (and has long supported PHP).  The days of Azure being for .NET devs only are long long gone and will never be back.  Azure is now a platform for anyone building apps of any sort with any technology.  Anyone that has come to this site for any Azure related resource over the past two years already knows that since I’ve been posting about connecting iOS and Android apps to Azure that whole time.  If anyone needed more convincing, I would point them to the Day 2 keynote from Build.  In that keynote you’ll see iOS apps (and iOS luminaries like John Gruber and Brent Simmons), you’ll see Java and .NET, you’ll even see something running in AWS. 

Azure is ready for all developers to work with.  I’m excited about the continued progress and potential as this platform becomes more open and more relevant to developers everywhere.  So, welcome to Microsoft Azure.

Categories: Azure, Microsoft
Bookmark and Share
First Article