This came up in the discussion of an nmdc-runtime PR (https://github.com/microbiomedata/nmdc-runtime/pull/572). Even though we're not claiming to be a full OAuth 2.0-compatible authorization server, I had intended to remain close to the standard where possible. I think it was just an oversight that I had used expires instead of the recommendedexpires_in as a field in the TokenResponse class.
Nothing in the front-end actually uses that value, so I think this is a fairly low-risk change. But I'd rather change it now before it hits production for the first time.
This came up in the discussion of an
nmdc-runtimePR (https://github.com/microbiomedata/nmdc-runtime/pull/572). Even though we're not claiming to be a full OAuth 2.0-compatible authorization server, I had intended to remain close to the standard where possible. I think it was just an oversight that I had usedexpiresinstead of the recommendedexpires_inas a field in theTokenResponseclass.Nothing in the front-end actually uses that value, so I think this is a fairly low-risk change. But I'd rather change it now before it hits production for the first time.