Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1434834

Summary: Implement automatic SSO token renew
Product: [oVirt] ovirt-engine-sdk-java Reporter: Juan Hernández <juan.hernandez>
Component: CoreAssignee: Ondra Machacek <omachace>
Status: CLOSED CURRENTRELEASE QA Contact: Radim Hrazdil <rhrazdil>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.1.3CC: bugs, juan.hernandez, lsvaty, mperina
Target Milestone: ovirt-4.2.4Flags: rule-engine: ovirt-4.2+
rule-engine: ovirt-4.3+
lsvaty: testing_ack+
Target Release: 4.2.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: java-ovirt-engine-sdk4-4.2.3 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-26 08:46:13 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1582077    

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.