Json support for Auth request about scala-redox HOT 2 CLOSED

Hey @AndrewZurn I have not seen the behavior your described before, sorry. That said, you make some reasonable suggestions:

• Change def authorize and def refresh to use Json rather than form-urlencoded
• Switch some of the private fields to protected to allow extension through inheritance

I'd prefer the first option, simply because once something is protected, you ideally want to keep things (mostly) backward compatible for anyone building off the Client.

Want to take a stab at changing the auth sequence to Json? Should be relatively straightforward. If not, I may get around to in the coming week.

from scala-redox.

I could probably get around to completing Option 1 early next week (I currently have it working in my own forked version for my company's project, so it should take long to replicate here).

I might take a stab at decoupling the authorization from the mechanism that stores it as to allow for some easier customization (I'll keep all of the current private members private).

Thanks!

from scala-redox.