The current implementation of our authentication API endpoint already adds the users' roles to the JWT token in the form of claims. This is all we needed to do in order to support role-based authorization on the server side of the application, as ASP.NET Identity automatically decodes the JWT for us so that the claims we added are available on the HttpContext.User.Identity claims principle object.
However, on the client side of our application, those claims are still encoded into the JWT and we cannot access them without decoding it. This isn't a huge issue, and we could certainly bring in a new npm package that would be able to decode a JWT for us, but we don't really need to. Instead, what we'll do is return the list of roles a user is assigned to as part of the view model we send back to the client when...
