Last post Jul 30, 2015 03:33 PM by progi
Jul 30, 2015 07:54 AM|maxbundchen|LINK
One of my projects requires additional data to authorization such as organization identity and a couple of other informations passed in the authorization process along the username and password. This project will be consumed by a web client and mobile apps
so I would like to use bearer token.
Should I add this additional values in the token as key pair values at the cost of increase this token? Should I enable session full at server side and store it as in a MVC project? Should I use additional header to store this additional information and
leave the bearer token as the default?
I know all this alternatives has ups and downs but I would like to know if anyone has experience or additional advice about this situation.
Jul 30, 2015 03:33 PM|progi|LINK
In may last project I toke the approach from this site:
I can recommend it.