0010442: RequestedLifetime not sent correctly in secure channel opening

ID	Project	Category	View Status	Date Submitted	Last Update

0010442	10000-004: Services	Spec	public	2025-07-17 16:02	2025-09-23 07:35

Reporter	Paul Hunkar	Assigned To	Matthias Damm
Priority	normal	Severity	major	Reproducibility	always
Status	closed	Resolution	fixed
Fixed in Version	1.05.06

Summary	0010442: RequestedLifetime not sent correctly in secure channel opening
Description	Problem Summary: The OPC UA client does not send the RequestedLifetime parameter correctly in secure channel opening requests, causing communication failures when the server returns a RevisedLifetime of 0. Impact: OPC UA communication is entirely blocked, and secure connections cannot be established. Action Required: Fix the client implementation to correctly send RequestedLifetime and handle scenarios where the server responds with unexpected values or 0 (default value sent).
Steps To Reproduce	Configure an OPC UA client to open a secure channel with an OPC server. Change the RequestedLifetime to 300000 Ensure the client sends a secure channel opening request with the RequestedLifetime parameter. To inspect the requests, you can use packet analysis software such as Wireshark. Observe the server's response. Check the default RequestedLifetime sent is 0 and the returned can be 0 (depends on server) Check if the RevisedLifetime returned is 0 and if the client throws the error BadInvalidArgument.
Tags	No tags attached.

Commit Version	1.05.06
Fix Due Date	2025-09-15

Paul Hunkar 2025-07-17 16:02 developer ~0023137	the initial change is that the the CTT should request something like 10 sec for the default. this issue should be cloned to test cases - we need to generate test cases for cases where server return a 0 (if a 0 is provided) - in general test cases around this issue this issue should also be clone to part 4 and ask for a clarification on - is it ok for a server to return a 0?

Paul Hunkar 2025-07-17 16:04 developer ~0023138	from the CMP group - need spec clarification

Jim Luth 2025-07-22 15:47 administrator ~0023155	Clarify that the Server is expected to provide a sensible non-zero revised lifetime. This also needs to be added to Session lifetime.

Matthias Damm 2025-09-22 16:58 developer ~0023326	OpenSecureChannel revisedLifetime Added The Server shall provide a sensible lifetime greater than 0. CreateSession revisedSessionTimeout Added The Server shall provide a sensible timeout greater than 0.

Jim Luth 2025-09-23 07:35 administrator ~0023329	Agreed to changes edited in F2F Meeting.

Date Modified	Username	Field	Change
2025-07-17 16:02	Paul Hunkar	New Issue
2025-07-17 16:02	Paul Hunkar	Status	new => assigned
2025-07-17 16:02	Paul Hunkar	Assigned To	=> Sebastian Allmendinger
2025-07-17 16:02	Paul Hunkar	Issue generated from: 0010441
2025-07-17 16:02	Paul Hunkar	Note Added: 0023137
2025-07-17 16:02	Paul Hunkar	Relationship added	related to 0010441
2025-07-17 16:03	Paul Hunkar	Project	CTT UA Test Case => 10000-004: Services
2025-07-17 16:03	Paul Hunkar	Category	2 - CTT Binary => Api Change
2025-07-17 16:03	Paul Hunkar	Assigned To	Sebastian Allmendinger =>
2025-07-17 16:03	Paul Hunkar	Category	Api Change => Spec
2025-07-17 16:04	Paul Hunkar	Assigned To	=> Paul Hunkar
2025-07-17 16:04	Paul Hunkar	Status	assigned => new
2025-07-17 16:04	Paul Hunkar	Note Added: 0023138
2025-07-22 15:47	Jim Luth	Note Added: 0023155
2025-07-22 15:47	Jim Luth	Assigned To	Paul Hunkar => Matthias Damm
2025-07-22 15:48	Jim Luth	Commit Version	=> 1.05.06
2025-07-22 15:48	Jim Luth	Fix Due Date	=> 2025-09-15
2025-07-22 15:49	Jim Luth	Status	new => assigned
2025-09-22 16:58	Matthias Damm	Status	assigned => resolved
2025-09-22 16:58	Matthias Damm	Resolution	open => fixed
2025-09-22 16:58	Matthias Damm	Fixed in Version	=> 1.05.06
2025-09-22 16:58	Matthias Damm	Note Added: 0023326
2025-09-23 07:35	Jim Luth	Status	resolved => closed
2025-09-23 07:35	Jim Luth	Note Added: 0023329