Details
-
Bug
-
Resolution: Fixed
-
P1: Critical
-
6.7.0
-
None
-
-
8
-
67b2aec9d (dev), 042561187 (dev), 649288461 (6.7), a4f8012a3 (tqtc/lts-6.5), 8b974b08e (tqtc/lts-6.2)
-
Foundation Sprint 108
Description
According to current native-application-OAuth best practice RFC the loopback port should be opened only when used for authorization request, and closed when done.
This best practice should be adopted when using QOAuthHttpServerReplyHandler; the close() should be called after authorization is complete, failed or otherwise. It should be possible to reopen to listen to the same port if later needed. Understandably if some other process in the operating system has already claimed the port in the meanwhile, it will just fail to listen, but this is acceptable (but it mustn't assert)
Note that the loopback listening is only needed when acquiring the authorization code. It is not needed when acquiring access token (neither for the first acquisition, nor for a token refresh). In other words:
- Authorization stage: callback/redirect_uri needed. Listening needed
- Request access token: callback/redirect_uri needed. Listening not needed
- Refresh access token: callback/redirect_uri not needed. Listening not needed
Attachments
Issue Links
- clones
-
QTBUG-124332 [OAuth] Access token expiration convenience functionality
- Closed
- is cloned by
-
QTBUG-124334 [OAuth OIDC] Qt OAuth2 for OpenIDConnect id_token acquisition
- Closed
-
QTBUG-125402 [OAuth] Investigate OAuth with QCoreApplication
- Closed