Bug 1434834 - Implement automatic SSO token renew
Summary: Implement automatic SSO token renew
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine-sdk-java
Classification: oVirt
Component: Core
Version: 4.1.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.2.4
: 4.2.3
Assignee: Ondra Machacek
QA Contact: Radim Hrazdil
URL:
Whiteboard:
Depends On:
Blocks: 1582077
TreeView+ depends on / blocked
 
Reported: 2017-03-22 12:56 UTC by Juan Hernández
Modified: 2018-06-26 08:46 UTC (History)
4 users (show)

Fixed In Version: java-ovirt-engine-sdk4-4.2.3
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-06-26 08:46:13 UTC
oVirt Team: Infra
rule-engine: ovirt-4.2+
rule-engine: ovirt-4.3+
lsvaty: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 91507 0 master MERGED Automatically replace bad tokens 2018-05-23 06:35:16 UTC
oVirt gerrit 91508 0 sdk_4.2 MERGED Automatically replace bad tokens 2018-05-23 07:47:04 UTC

Description Juan Hernández 2017-03-22 12:56:11 UTC 
Currently when the SSO token used by the SDK expires, the operations just fail, and the only way to recover is to close the connection and open a new one. This isn't convenient, specially for long running applications. The SDK should have a mechanism to automatically renew the SSO tokens when they expire.
Comment 1 Ondra Machacek 2018-05-17 15:59:10 UTC 
Error exception should also containt HTTP response code.
Comment 2 Radim Hrazdil 2018-05-31 11:22:07 UTC 
Verified that periodic query with interval higher than UserSessionTimeOutInterval leads to Receiving response: HTTP/1.1 401 Unauthorized and subsequent re-authorization. SSO token is renewed correctly.

java-ovirt-engine-sdk4-4.2.3-1.el7ev.noarch
Comment 3 Sandro Bonazzola 2018-06-26 08:46:13 UTC 
This bugzilla is included in oVirt 4.2.4 release, published on June 26th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.4 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.
Note You need to log in before you can comment on or make changes to this bug.