I want to use asp.net identity as my web api authentication provider and authorization server, but there is only one thing that make me skeptical and hesitate more about using it, which is it's long token (512 bit), I also Implemented ISecureDate interface and customize my token generation using JWT but I only managed to reduced my token length to 483 (which is not much different from default Microsoft token length), Because most of our apis are authorized so the users will send the long (512 bit) token in every request, keep it in mind that performance is a key factor for our web app and since we're living in Iran,the inteet speed is considerably slow (in comparison with other countries) so we have keep every thing as minimal as possible in our requests and responses. My question is how much a 512 bit bearer token could affect the coection speed (especially in our circumstances) because if it's much I have to leave Owin and asp.net Identity behind and write my own authentication provider and in addition to writing my authentication logic I would have to override some attributes inside of MVC such as "Authorize" but it's to time consuming (as if i'm reinventing the wheel) and no as good as asp.net identity. In other word is sending long token effect on coection speed that much that I have to use my own authentication (I repeat again in our circumstances(inteet speed) not in general) leave Owin and asp.net Identity behind and not to use their benefits, Is it really worth it (when performance is a critical factor)????
I'd be happy to know your opinions