This issue is limited only to the creator of this issue. This means that only the issue author can attempt to solve this issue. If you would like to work on it, please create another issue with the same contents and refer to issue #743 for more information.
Problem
registerUser generates the response id and the JWT sub with separate Date.now() calls. If those calls differ, the API returns a user id that does not match the authenticated subject embedded in the token.
Expected
Registration should generate one user id and use that same id in the returned payload and the signed token subject.
Scope
Only registration id/token-sub consistency and regression coverage.
This issue is limited only to the creator of this issue. This means that only the issue author can attempt to solve this issue. If you would like to work on it, please create another issue with the same contents and refer to issue #743 for more information.
Problem
registerUsergenerates the responseidand the JWTsubwith separateDate.now()calls. If those calls differ, the API returns a user id that does not match the authenticated subject embedded in the token.Expected
Registration should generate one user id and use that same id in the returned payload and the signed token subject.
Scope
Only registration id/token-sub consistency and regression coverage.