Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Server returns BadSessionNotActivated when closing a not activated session #2143

Open
7 tasks
jonasgreen88 opened this issue Oct 26, 2018 · 0 comments
Open
7 tasks

Comments

@jonasgreen88
Copy link
Contributor

Description

This issue was discovered by a client developer during the OPC IOP Workshop when he failed to active the session due to wrong username/password.
The OPC UA Specification Part 4 (1.04), chapter 5.6.4, says:

When the CloseSession Service is called before the Session is successfully activated, the Server shall reject the request if the SecureChannel is not the same as the one associated with the CreateSession request.

So I think in other cases the CloseSessionRequest shall be processed with good result, even if it has not been activated.

Also, if the authenticationToken of the of the CloseSessionRequest doesn't match the session of the currently used secure channel the stack calls the function getSessionByToken(). According to the specification the CloseSessionRequest should be rejected in this case.

Background Information / Reproduction Steps

Create a session and the close it without activating it first.

Checklist

Please provide the following information:

  • open62541 Version (release number or git tag): cce2d62
  • Other OPC UA SDKs used (client or server):
  • Operating system:
  • Logs (with UA_LOGLEVEL set as low as necessary) attached
  • Wireshark network dump attached
  • Self-contained code example attached
  • Critical issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant