Imported Google Group message.
Sender:Martin Buhr
.
Date:Saturday, 25 July 2015 10:48:49 UTC+1.
Ok, we found the bug an have added a new test to cover it off 
Basically, the library we use to handle Oauth requests, has a very odd data structure, it uses an embedded object structure where it tails itself on refreshes (!!), this nested reference also references a pointer to an interface, interfaces can't be decoded in JSON since they don't have explicitly exported types (they are just function signatures), they can be encoded (because the marshaller just takes the underlying struct and marshals the data), but they cannot be unmarshaled, because it doesn't know what the data structure looks like (there isn't one!)
This is fine if everything is happeining in memory, but not when the objects are serialised, and especially if you don't know how "deep" they are.
So we've modified things to have a custom unmarshaller that explicitly initialises the interface before decoding, and now it works and it seems to all be in order now.
The release is here: https://github.com/lonelycode/tyk/releases/tag/1.7.3
Tests are passing. Docker images are building.
Let me now how you get along with it!
Cheers,
Martin
On Saturday, July 25, 2015 at 2:14:44 AM UTC+1, Pascal Combescot wrote:
Great !
We are really pleased by the product otherwise. And it seems we will be the first to put the Oauth process with Tyk in production (at least the authorization_code process) 