-
Bug
-
Resolution: Fixed
-
P2: Important
-
6.5, 6.8
-
None
-
All
-
3
-
44576daf9 (dev), 3807bb434 (6.9), 27ddc092f (6.8), 5612c9525 (tqtc/lts-6.5)
-
Foundation Sprint 121
OAuth2 expirationAt doest not change when invalidated.
If we first get a valid expires_in from the authorization server, and then later an invalid one, the expiresAt remains at the value it first received. This is misleading because it implies to the application that the new token has an expiration time, which is not true.
| For Gerrit Dashboard: QTBUG-131948 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 609710,5 | Change QAbstractOAuth2::expirationAt also when invalidated | dev | qt/qtnetworkauth | Status: MERGED | +2 | 0 |
| 610300,2 | Change QAbstractOAuth2::expirationAt also when invalidated | 6.9 | qt/qtnetworkauth | Status: MERGED | +2 | 0 |
| 610405,3 | Change QAbstractOAuth2::expirationAt also when invalidated | 6.8 | qt/qtnetworkauth | Status: MERGED | +2 | 0 |
| 610700,2 | Change QAbstractOAuth2::expirationAt also when invalidated | tqtc/lts-6.5 | qt/tqtc-qtnetworkauth | Status: MERGED | +2 | 0 |