Consider returning actual JWT during OAuth token emulation

[drub0y]

Is your feature request related to a problem? Please describe. Today, when relying on the emulator to do "full" OAuth emulation, the token that is returned is in the form of "emulator_<hash>" instead of an actual JWT token. This forces the developer to have to detect emulator tokens themselves and provide their own "fake" JWT to be used by downstream logic.

Describe the solution you'd like I would love to see the emulator create a JWT token on the fly which would normalize the code path for the developer even when using the OAuth emulation feature.

Describe alternatives you've considered The only alternative I know of is manually checking the resulting token to see if it starts with "emulator_" and, when it does, go down a separate code path that creates a "fake" JWT token myself so that my downstream logic always deals with a JWT token.

[enhancement]