After our discussion here: Integrating with an old OAuth2 NancyFX API
I decided to at least look at what the long term solution looks like. My thought process is that if we can drop-in replace the old API and start handing out Jwt tokens from SS, any old mobile clients that try to hit the API with an old token would essentially require “re-authenticating”, and then get a new SS JWT token. Somewhat transparently.
But this project uses string ids for the Users table. To make matters worse, the string is populated with a guid in the database lol.
When I went to inherit our User object from IUserAuth, I discovered this.
I’m trying to discern if I’m in for a world of hurt trying to make this work? Should I just convert to a real Guid or integer id? Or if there is a better way?
My last SS project fully replaced the IUserAuth, AuthRepository, and AuthProvider (it already had int ids for the Users). But this might be overkill.
- Maybe I don’t need to inherit from IUserAuth to implement a custom AuthProvider?
- Is the only time IUserAuth inheritance needed is when implementing a custom AuthRepository?
- Is it even a typical scenario to inherit my Project.ServiceModel.Types.User class from UserAuth / IUserAuth?