Repository navigation
Releases
go-opcua v1.33.0
Date: 2026-11-15
Previous release: v1.32.1
The client verifies the endpoint list it selected its endpoint from with the ServerEndpoints of CreateSession (Part 4 §5.6.2), the server answers GetEndpoints and CreateSession with the same endpoints for the same URL, the batch helpers take a response only with one result per operation, and the PubSub JSON mapping bounds a String PublisherId as UADP does. Changes that need attention when upgrading: a client whose endpoint came from GetEndpoints refuses a server whose CreateSession endpoints differ from that answer (see Breaking).
Breaking
- A client compares the
GetEndpointsanswer it selected its endpoint from with the ServerEndpoints of the CreateSession response (Part 4 §5.6.2), when the endpoint given toSecurityFromEndpointis one of the endpointsopcua.GetEndpointsorClient.GetEndpointsreturned. The lists differ when an endpoint of one has no endpoint in the other with the same security policy, mode and level, transport profile, user token policies, application URI (when both name it) and certificate (as bytes, when both carry one); their order and the endpoint URLs are not compared. On a difference, Connect closes the session before ActivateSession and fails with an error matchingua.StatusBadSecurityChecksFailed. A server that returns other endpoints in CreateSession than in GetEndpoints is refused, and so is, on a reconnect, a server whose endpoints changed since the client discovered them.opcua.InsecureSkipDiscoveredEndpointsCheck()restores the behaviour of v1.32.1.
Added
opcua.DiscoveredEndpoints(endpoints): the endpoint list the client selected its endpoint from, compared with the ServerEndpoints of every CreateSession as above. It takes precedence over theGetEndpointsanswer and serves endpoints that are copies or come from elsewhere. After a server certificate change the client compares with the endpoints it fetches again.opcua.InsecureSkipDiscoveredEndpointsCheck(): turns the comparison of the list off, wherever the list comes from. The comparison of the endpoint given toSecurityFromEndpointstays.jsonmsg.MaxCorrelationData(4096): the longest CorrelationData, String PublisherId and String RequestorId the JSON decoder accepts. The UADP decoder uses the same bound.
Fixed
- client:
ReadMulti,ReadValues,WriteValuesandNode.Attributes(and soNode.Summary) take a response only when it holds one result per operation of the request, in every chunk of aReadMulti; a response with another number of results fails with an error matchingua.StatusBadUnknownResponse. - server: GetEndpoints (Part 4 §5.4.4) and CreateSession (§5.6.2) select the endpoints of the URL the client named in the same way: the scheme and the host compared without regard to letter case, one trailing slash ignored, the path compared as it is; when no endpoint has that URL, both return all endpoints. A client that names a server with opc.wss or opc.https endpoints next to opc.tcp with another letter case for the host or with a trailing slash gets the same endpoints from both services, and so connects with the comparison above.
- pubsub JSON: a String PublisherId (of a NetworkMessage, a DataSetMessage, a metadata, status or action message) or a String RequestorId of more than 4096 bytes is a decode error, as in UADP.
go-opcua v1.32.1
Date: 2026-11-14
Previous release: v1.32.0
Bounds on the work and memory of decoding: Variant arrays, AMQP 1.0 messages, PubSub metadata, chunk reassembly and PKCS #12 files; limits on GDS query patterns and SecurityGroup key counts; and 32-bit builds that handle lengths, enumeration names and NodeSet2 integer attributes as 64-bit builds do. No API changes.
Fixed
- UA Binary: a Variant array is never longer than the bytes that follow its length (every element takes at least one byte); a longer one is refused before it is allocated. The decoding of an array and of its ArrayDimensions stops at the first element that does not decode.
- UA Binary: the length of a String, ByteString or ExtensionObject body is compared with the remaining input as an unsigned number, so 32-bit builds take the same lengths as 64-bit builds.
ua.Buffer.ReadNwith a negative count fails withio.ErrUnexpectedEOF, as with more bytes than are left. - server: the length at the start of a legacy encrypted user password is compared with the decrypted bytes as an unsigned number (
Bad_IdentityTokenInvalidwhen they cannot hold it), and a MaxNotificationsPerPublish above the largestintof a 32-bit build is taken as that largest value, as on 64-bit builds. - ua: the String method of an enumeration with an unsigned type gives
Type(n)for every value that has no name on 32-bit builds too.make genkeeps this when it regenerates the methods. - server: the NodeSet2 import reads the integer attributes ValueRank and the
Valueof a DataType field as 64-bit numbers, so 32-bit and 64-bit builds accept and refuse the same files. - pubsub AMQP: the element counts of the nested lists, maps and arrays of an AMQP 1.0 message share one budget, the bytes of the message, so decoding allocates in proportion to the message size.
- GDS: the 4096-byte limit of a QueryApplications or QueryServers pattern is checked before the pattern is compiled, and consecutive
%compile as one. - pubsub JSON: a reader looks the field names of a DataSetMessage up in an index of its DataSetMetaData, built once for each DataSetMetaData, and the JSON decoder builds one index per DataSetMetaData of a NetworkMessage. A DataSetMetaData from the network (
ua-metadata, or a UADP discovery announcement) with more than 65535 fields is a decode error. - pubsub JSON: an unsigned integer of 2^64 or more in exponent or fraction notation is refused, as it is in plain notation.
- pubsub security:
KeyService.AddSecurityGrouprefuses aMaxPastKeyCount+MaxFutureKeyCountabove 65534 withBad_InvalidArgumentbefore it generates keys, so the keys of a SecurityGroup fit the Keys array of one GetSecurityKeys result. - pubsub UADP: the structure type cache of RawData fields keeps only the NodeIds that have a registered Go type.
- pubsub UADP: the decoder refuses a String PublisherId and a CorrelationData of more than 4096 bytes, and a
Reassemblercharges the first chunk of a message with its String PublisherId, String RequestorId and CorrelationData, which the message keeps while chunks are missing. - uapolicy:
ParsePFXcharges a key derivation its iterations times the blocks of hash output it derives against the work limit, and refuses a PBMAC1 key length above the block size of its HMAC.
Tests
- conformance/addrspace:
TestView_MapNamespaceservesmath.MaxIntas its Gointvalue, where it served a constant that did not fit theintof a 32-bit build, so the package builds and its tests run on 32-bit builds.
Notes
- v1.32.0 added
DomainNames []stringtogdsserver.PendingRequest, so values of the type can no longer be compared with==(the API check against v1.31.0 reports it). Code that compared them compares the fields it needs. Nothing in the code changes.
go-opcua v1.32.0
Date: 2026-11-13
Previous release: v1.31.0
Stricter server defaults and more limits, checks of session and certificate state, and the MessageNonce sequence of secured PubSub. Changes that need attention when upgrading: the server limits the operations per request to 32 by default, serves Node Management and Query only when enabled, serves a session only on its own SecureChannel, and a client checks the CreateSession ServerEndpoints against the endpoint it chose. This release also contains the fixes prepared as v1.31.1, which was not released.
Added
- server:
WithOperationLimits(OperationalLimits). The server enforces the OperationLimits it publishes (Part 5 §6.3.11): a request with more operations than its limit fails withBad_TooManyOperations(Part 4 §7.38). The default is 32 for every limit; a field set to 0 has no limit. - server:
EnableNodeManagement()to serve AddNodes, AddReferences, DeleteNodes and DeleteReferences, and theNodeManagementAccessControllerinterface to authorize each operation;RBACAccessControllerimplements it. Without the option they returnBad_ServiceUnsupported. - server:
WithQuery(bool)to serve QueryFirst and QueryNext. When enabled, Query applies the Browse, Read and AccessRestrictions checks of the nodes it returns. - server:
WithMaxMonitoredItems(default 100000),WithMaxMonitoredItemsPerSubscription(10000) andWithMaxMonitoredItemsPerSession(20000); CreateMonitoredItems beyond them fails withBad_TooManyMonitoredItems. - server:
WithMaxBrowseContinuationPoints(default 10) andWithMaxQueryContinuationPoints(default 5) per session. ua.MaxBinaryNestingDepth(100): the nesting depth of UA Binary values.uapolicy.VerifyCertificateChains: the verified chains of a certificate.gdsserver.PendingRequest.DomainNames: the host names a pending certificate request will be issued for.- pubsub:
WithNonceSequencePerToken,Counters.NonceSequenceDiscardsanduadp.EncodeOptions.NextNonceSequenceForToken.
Changed
- server: Node Management and Query are off by default (see Added). Servers that offer them call
EnableNodeManagement()orWithQuery(true). With Node Management on and noNodeManagementAccessController, clients cannot change namespace 0. - server: a request carrying the AuthenticationToken of a session on another SecureChannel fails with
Bad_SecureChannelIdInvalid(Part 4 §5.7.3), CloseSession included. The first ActivateSession has to come over the channel of CreateSession; a later one moves the session to a new channel when that channel has the same security policy, mode and client certificate and the user is the same (Bad_IdentityChangeNotSupportedotherwise, §5.7.3.1). A client that reconnects keeps its session as before. On opc.https and UA JSON over opc.wss a session is tied to its security policy. - server: an X.509 user token policy on an endpoint with security None names a SecurityPolicy (Part 4 §7.40.5): the enabled RSA policy with the highest SecurityLevel, else the highest ECC one. When only None is enabled, no X.509 user token is offered. An X.509 token whose policy is None is rejected with
Bad_IdentityTokenRejected. - server: an LDS registration over a channel without a client certificate (opc.https, UA JSON over opc.wss) needs
LDSAllowInsecureRegistration, also withLDSSkipServerURICheck. - server: HistoryRead and HistoryUpdate of data are authorized per node, as Read and Write are: the AccessController, AccessRestrictions and the HistoryRead/HistoryWrite bits of AccessLevel. CreateMonitoredItems on a data item applies the checks of Read.
- server: NodeSet2 variables without AccessLevel are CurrentRead, the schema default, and the Server object's own variables are CurrentRead; before, clients could write them.
- server:
Node.SetAttributeno longer refuses a Value on AccessLevel, so server code can update read-only values. Client writes andNodeNameSpace.SetAttributeare checked as before. - server: the PubSub configuration methods check their TargetVariables and PublishedVariables against the calling session, target attributes other than Value obey WriteMask and DataType, and under
RBACAccessControllerthe methods need ConfigureAdmin. Password and secret ConnectionProperties read as null in the address space. - server: Republish and the acknowledgements of a Publish name subscriptions of the calling session only; others fail with
Bad_SubscriptionIdInvalid. - server: Browse and Query continuation points belong to their session, are limited per session (
Bad_NoContinuationPoints), expire after 10 minutes without use and are released with the session. - server: event monitored items with QueueSize 0 get a queue of 1000 (was 1), at most 10000. A full queue discards an event as its DiscardOldest says and marks the place with an EventQueueOverflowEventType event (Part 4 §5.12.1.5). Events count against MaxNotificationsPerPublish.
EmitEventandEmitBaseEventnever block; their wait argument has no effect. - server: a ContentFilter or EventFilter with more than 256 elements is refused.
- client: CreateSession compares the ServerEndpoints of the response with the endpoint given to
SecurityFromEndpoint(Part 4 §5.6.2): application URI, security policy and mode, SecurityLevel, transport profile and user token policies. A mismatch fails the connection withBad_SecurityChecksFailedand closes the session. An EndpointDescription built by hand has to match the server's. - UA Binary values nested deeper than 100 Variant, DataValue, DiagnosticInfo and ExtensionObject levels fail to decode and encode with
Bad_EncodingLimitsExceeded, as in the JSON and XML codecs. - uasc: a SecureChannel holds the chunks of at most 16 incomplete messages, and at most twice the largest message it accepts; beyond that the connection is closed with
Bad_TcpMessageTooLarge. - uacp: a connection accepted by
uacp.Listenerthat does not send OpenSecureChannel within 10 s of the HEL/ACK is closed. - GDS: the host names of a certificate are fixed when the request is made, from the request or the DiscoveryUrls of the application at that time. DiscoveryUrls with wildcard hosts are refused with
Bad_InvalidArgument. Requests stored by an earlier version keep the DomainNames they stored. - Push management: the revocation of issuers is checked along the verified certificate chains.
- Certificate chains with Ed448 signatures: the search for a path verifies at most 100 signatures and looks at at most 10000 candidates; duplicate intermediates are ignored.
- pubsub: secured UADP messages (PubSub-Aes128-CTR, PubSub-Aes256-CTR) whose MessageNonce sequence number is not newer than the last one of their sender and SecurityTokenId are ignored (Part 14 §7.2.3, Table 156): DataSetMessages, chunks, and Action requests and responses. They count as
NonceSequenceDiscards. A publisher restarted on the same token is taken again after twice the MessageReceiveTimeout, or withWithNonceSequencePerTokenat the next token. - pubsub: senders start the MessageNonce sequence at 1 for every SecurityTokenId (Table 156); before it never started over.
- pubsub: a DataSetMessage sequence number a quarter of the number space or more ahead is ignored (
SequenceDiscards) instead of resynchronising;SequenceResyncscounts resynchronisations after a sender's record expired. Reader sequence records expire after twice (was once) the MessageReceiveTimeout. - pubsub: reassembly discards a message whose chunks conflict, or whose GroupHeader numbers differ between chunks, and keys chunks by SecurityTokenId.
Fixed
- server: an OpenSecureChannel refused for an untrusted client certificate is reported to the
SessionObserverand audited before the client receives the Error message. Before, the client could see the refusal first. - A decrypted chunk whose padding size exceeds its length fails with
Bad_SecurityChecksFailedinstead of panicking. A panic on the client's receive goroutine ends the channel, and its pending requests fail withBad_InternalError, instead of ending the process. - server: the session limit of v1.31.0 (
WithMaxSessions, 100 by default) filled up with sessions their clients had left behind. A client that loses its connection cannot close its session, which then stays until its session timeout (up to 30 minutes), so on an unreliable network the server soon refused every new client withBad_TooManySessions. A full server now closes the session whose secure channel has been gone longest to make room, asSessionClosedByServerfor theSessionObserverand an audit event of a terminated session. A session on an open channel is never closed for it, so a client that can create sessions cannot push others out. opc.https and UA JSON over opc.wss have no connection that closes, so there an abandoned session cannot be told from an idle one: a full server closes the one unused longest once it has been unused for 30 s, after the sessions of closed channels. A client that keeps such a session sends Publish requests, or reads to keep a session without subscriptions alive, more often than that. A client that comes back to a closed session getsBad_SessionIdInvalidand creates a new one. - client: a client that gave up on its session after a fault created a new one without closing the old one, which the server kept until its timeout. It now closes it first (best effort, keeping the subscriptions for the transfer to the new session, Part 4 §5.6.4). A server that refuses the new session with
Bad_TooManySessionsis asked again after a wait that starts atReconnectIntervaland doubles up to 30 s, instead of everyReconnectInterval. - server: closing a session took time quadratic in the number of sessions with diagnostics, because removing a reference compared NodeIds through their strings, and the type and summary nodes reference every session's diagnostics. With many clients coming and going, the one goroutine that handle...
go-opcua v1.31.0
Date: 2026-11-03
Previous release: v1.30.0
Findings of a static analysis review: defects, limits that were only kept by a check elsewhere and are now checked where the value is converted, and server limits that were missing. Three changes need attention when upgrading: the server limits sessions and subscriptions, clients can write attributes other than Value only where the node's WriteMask allows it, and both sides keep to the message size and chunk count the peer announced.
Added
- server:
WithMaxSessions(default 100),WithMaxSubscriptions(default 1024, all sessions) andWithMaxSubscriptionsPerSession(default 64), the defaults of open62541. They are published as ServerCapabilitiesMaxSessions,MaxSubscriptionsandMaxSubscriptionsPerSession(Part 5 §6.3.2). Before, the number of sessions and subscriptions was unbounded, and a client that never activated its sessions could fill memory. uacp.Conn.PeerMaxMessageSizeandPeerMaxChunkCount: the limits the peer announced for what it receives.message.PublisherID.Validate: checks the type and that a numeric PublisherId fits it.uadp.Encodeand the PubSub configuration use it;PublisherID.Variantstill truncates, so callValidatefirst.
Changed
- server: CreateSession fails with
Bad_TooManySessions(Part 4 §5.6.2) once the server keepsWithMaxSessionssessions, activated or not; a closed or timed-out session frees its place. CreateSubscription fails withBad_TooManySubscriptions(§5.13.2) at the server-wide or the per-session limit. TransferSubscriptions answersBad_TooManySubscriptionsfor a subscription that would take the session past its limit and leaves it where it was. - server: the Write service enforces the WriteMask of a node for every attribute other than Value (Part 3 §5.2.7, §8.60). Without its bit, a write is
Bad_NotWritable; a UserWriteMask on the node narrows it further (Bad_UserAccessDenied, §5.2.8). Nodes built with the Go API have no WriteMask, so clients can write only their Value, as in UA-.NETStandard and open62541. Before, a client could overwrite NodeClass, BrowseName, EventNotifier, DataType and the others with any value. To open DisplayName, Description and the others, setua.AttributeIDWriteMask(UInt32) on the node; a customNameSpacereturns it fromAttribute. NodeSet2 imports keep their WriteMask, and AddNodes now keeps the WriteMask and UserWriteMask the client sends. NodeId and NodeClass are never writable; UserRolePermissions isBad_NotWritable, and an unknown AttributeId isBad_AttributeIdInvalid. - uasc: the client sends no request above the MaxMessageSize or MaxChunkCount of the server's Acknowledge (Part 6 §7.1.2.4) and fails it with
ErrMessageTooLargeandBad_RequestTooLarge. The server aborts a response above the limits of the client's Hello (§7.1.2.3) with an abort chunk carryingBad_ResponseTooLarge, so the client gets that status at once and the channel stays open. Before, the server sent the response and the client discarded it withErrTooManyChunksorErrMessageTooLarge. - The client's
MaxMessageSizeandMaxChunkCountoptions cap what it accepts even if the server announces more. Left at 0, the client takes the server's limits, or 512 chunks and 2 MiB when the server has none, as before; a server that announces MaxUint32 no longer raises them. With default settings nothing changes on the wire. - server:
NodeNameSpace.SetAttributeapplies AccessLevel only to the Value attribute (Part 3 §5.6.2). Before, a read-only Value also made the node's other attributes read-only. server.DataValueFromValueand the server's own values encode a Gointoutside the Int32 range as an Int64. Before, it was truncated to an Int32.server.Server.AddNamespacerefuses a namespace beyond the 65536 that a UInt16 NamespaceIndex can address (Part 3 §8.2.2): it logs an error and returns -1. A NodeSet2 import that would pass that limit fails before it adds a namespace.- The PubSub configuration refuses a PublishedDataSet with more than 65535 fields (Part 14 §7.2.4.5: FieldCount and the field index are UInt16). Before, the key frame failed to encode, but the delta frames after it went out with wrapped field indexes.
jsonmsg.DecodeOptions.MaxFieldsis capped at 65535 for the same reason. uadp.Encoderefuses a chunk with no ChunkData or ChunkData beyond TotalSize, as the decoder does, and a PublisherId wider than its type.opc.httpsresponses carryX-Content-Type-Options: nosniff.
Fixed
- server: a write of an attribute other than Value with a value of the wrong DataType (a String for EventNotifier, an Int32 for NodeClass) is refused with
Bad_TypeMismatchinstead of being stored. A write of the Value of aMapNamespacekey with no value returnsBad_TypeMismatchinstead of dereferencing a nil Variant. - The client's AMQP transport read a broker's incoming window or link credit of 2^31 or more, MaxUint32 for "unlimited" among them, as negative and stopped sending (AMQP 1.0 §2.5.6, §2.6.7: they are counts, not serial numbers). PubSub publishing over such a broker stalled.
- The client's MQTT transport wrote a client identifier, user name, password or will payload over 65535 bytes with a wrapped two-byte length (MQTT §1.5.4, §1.5.6), and the broker read its tail as the following fields.
Dialand the encoder now refuse it. Client.NodeFromQualifiedPathaccepted a namespace index above 65535 ("70000:Name"), which its documentation excludes, and addressed namespace 4464. It now refuses it.- server: a DataType whose numeric id ends in the byte of a built-in number (DiagnosticsLevel i=19723, ContinuationPoint i=521, ...) counted as numeric, so an absolute or percent deadband on such a Variable was accepted instead of
Bad_FilterNotAllowed(Part 4 §7.22.2). - server: an event filter's BitwiseAnd and BitwiseOr with a UInt64 operand returned an Int64, so results of 2^63 and above compared as negative (Part 4 §7.4.3: the result has the size of the larger operand). They now return a UInt64.
- server: a NodeSet2 file with an AccessLevel or UserAccessLevel above 255 or a ValueRank outside Int32 had the value truncated; an AccessLevel of 259 became CurrentRead|CurrentWrite. Such values are now skipped with a warning. An EventNotifier stored as an Int32 or UInt32 outside 0..255 reads as 0.
- uasc: a server or
uacp.Listenerconfigured with MaxChunkCount or MaxMessageSize 0, which Part 6 §7.1.2 defines as no limit, refused every message of more than one chunk, or every message. Zero now means no limit. - uasc: after a message was refused for too many chunks or bytes, its remaining chunks were collected again and merged with its final chunk into a message of their own. They are now dropped up to the final chunk.
- uasc: a message of many chunks is refused with
ErrMessageTooLargeas soon as its chunks pass MaxMessageSize, not after all of them are collected. Message sizes are compared without truncation, a chunk that cannot fit the UInt32 MessageSize is refused on send, and uacp compares the send size before converting it. - ua: a multi-dimensional array whose element count passes Int32, an ExtensionObject body over 2 GiB, and an unsigned enumeration or option set value above MaxInt64 in JSON and XML were encoded with wrapped or negative lengths or values. The first two now fail with an encoding error; the third is written and read as an unsigned number.
Node.NodeClassrefuses a NodeClass outside UInt32 from a server instead of truncating it. SessionLifetimeand the request TimeoutHint are clamped to the UInt32 milliseconds they are sent in.- PubSub: received RawData with a zero dimension in a multi-dimensional array or a dimension above Int32 is refused in the UADP decoder. The MQTT transport compares a MaximumPacketSize property above 2^31 correctly on 32-bit platforms.
- Examples:
examples/cryptowrote the generated private key world-readable (0644), now 0600; three example servers wrote their certificate and key with mode 0, so they could not read them back. The PubSub and translate examples refuse a PublisherId or namespace flag outside UInt16 instead of truncating it.
go-opcua v1.30.0
Date: 2026-11-02
Previous release: v1.29.5
Added
server.WithSessionObserverandserver.SessionObserver: the application is told about client connections (OnConnectionOpened,OnConnectionClosedwith the duration) and sessions (OnSessionActivated,OnSessionClosedwith the reasonSessionClosedByClient,SessionTimedOutorSessionClosedByServer) where they happen, with the session name, the client's ApplicationDescription, the endpoint, the client's address, the security and the user (SessionInfo). Before, a server could only find out about its clients by polling the session diagnostics or parsing its log.server.BaseSessionObserverimplements the interface with no-op methods for embedding.SessionObserver.OnRejectedandserver.Rejection: the observer is also told about the requests the server refused: an OpenSecureChannel (an untrusted client certificate), a CreateSession, an ActivateSession (a wrong password, a token type no endpoint offers), with the status, the client's address, the security, the client certificate and, for the sessions, the session name and the identity the client tried.- Security audit events (Part 4 §6.5.5, §6.5.6; Part 5 §6.4): with
WithAuditing(true)the server reports AuditOpenSecureChannelEventType (opened channels and every failed OpenSecureChannel), AuditChannelEventType (CloseSecureChannel), AuditCreateSessionEventType and AuditActivateSessionEventType (every call, refused ones too), AuditSessionEventType (Session/CloseSession,Session/Timeout,Session/Terminated) and the AuditCertificateEventType subtypes of a refused certificate, which the failed AuditOpenSecureChannelEventType names in CertificateErrorEventId. The user identity token of AuditActivateSessionEventType carries no password or issued token data. Before, only the condition methods, the GDS andReportAuditEventraised audit events. uasc.Config.OpenSecureChannelHook: a server channel reports every OpenSecureChannel request it handled and the status it answered with.
Changed
Session.Identity()(andMethodCaller.Identity) no longer carry the password of a UserNameIdentityToken: the session does not keep it. The doc comment said the password was still encrypted; it was the clear text. TheRoleMapperstill gets the token with the password.
Fixed
- server: a rejected ActivateSession changed the user identity of the session to the one it rejected (Part 4 §5.6.3 leaves the session as it was). A client of an activated session that sent ActivateSession with another user's name and a wrong password got
Bad_UserAccessDenied, but the session then reported that user inSession.Identity(), which anAccessControllermay decide on, and counted as that user's session for TransferSubscriptions. The roles were not affected. The session now takes an identity only once it has been accepted. - server: ActivateSession accepted every user token type, also those no endpoint offers (Part 4 §5.6.3: the EndpointDescription says which UserIdentityTokens the server accepts). A server that offers only user names let in anonymous clients, and one that offers user names only on secured endpoints accepted a clear text password over a None channel. A token type is now accepted only if an endpoint of the client's channel (same security policy and mode; opc.https and opcua+uajson for their virtual channels) offers it, else
Bad_IdentityTokenRejected. A null or empty token counts as anonymous, as Part 4 says; before, it kept the identity of the previous activation. A token that is no user identity token isBad_IdentityTokenInvalid.
go-opcua v1.29.5
Date: 2026-11-02
Previous release: v1.29.4
Fixed
- HistoryUpdate DeleteEventDetails answers an EventId without an event with
Bad_NoEntryExists(Part 11 §6.2.2), as UA-.NETStandard does, notBad_NoData. When no event matches any of the EventIds, the node status isBad_NoData(§6.9.7.2). A client that tests forBad_NoDataper operation has to test forBad_NoEntryExists. - With a client certificate trust list, CreateSession on a channel with SecurityPolicy None refused a client that sent a certificate the list does not trust (
Bad_SecurityChecksFailed). The server now ignores that certificate, as Part 4 §5.7.2.2 says;Session.ClientCertificateis nil on such a session. The node-opcua client sends its certificate there. - The UserName token policies of opc.https endpoints, and of opc.wss None endpoints, name the security policy that encrypts the password (Part 6 §7.4.1): a secured opc.https endpoint its own, a None endpoint the strongest enabled RSA policy whose certificate it carries (Part 4 §7.41). The password no longer goes in clear text inside TLS when such a policy is enabled, and the UA-.NETStandard client, which refused to send it (
Bad_SecurityChecksFailed), can log in. Without an enabled RSA policy, and on opc.tcp, nothing changes. - A value a client writes gets the time the server received it as its SourceTimestamp (Part 4 §7.11.3), and the PubSub publisher stamps the ServerTimestamp of a value it samples, as a Read does (§7.11.4). Before, a written value had neither: a Read with TimestampsToReturn Source returned no timestamp, and a PubSub DataSetMessage left out the timestamps its DataSetFieldContentMask selects. With the trigger StatusValueTimestamp and no deadband, a write of the same value is now a data change: its SourceTimestamp changes.
go-opcua v1.29.4
Date: 2026-11-02
Previous release: v1.29.3
Fixed
- A server no longer refuses a Hello whose EndpointUrl names another port than the one it listens on with
BadTcpEndpointUrlInvalid. A server behind a published port or a proxy could not be reached (docker run -p 5000:4840). The scheme, host and path are still compared. - A Read or Write that the AccessLevel of a node rules out now answers
BadNotReadableorBadNotWritable(Part 4).BadUserAccessDeniedremains for what only the UserAccessLevel or the access controller rules out. A client that tests forBadUserAccessDeniedon such a node has to test for the new status.
Added
server.Node.AccessStatus, the status of a read or write of the node.
go-opcua v1.29.3
Date: 2026-11-01
Previous release: v1.29.2
Security
- A TLS client certificate removed from the DefaultHttpsGroup trust list could still connect to
opc.httpsandopc.wssendpoints by resuming a TLS session saved while it was trusted, withHTTPSClientCertificatesset to verify or require. The trust list is now checked on every connection. Affects v1.18.0 to v1.29.2. See advisory GHSA-5mpv-gmwr-mmh5.
Changed
- With
HTTPSClientCertificatesset to verify or require, the check runs intls.Config.VerifyConnection. AVerifyConnectionin the given TLS configuration still runs, after the trust list.
go-opcua v1.29.2
Date: 2026-10-31
Previous release: v1.29.1
Changed
- Tests, CI and documents only.
make coverage-gateis nowmake coverage-pkg-check, andmake exampleswrites tobin/.
go-opcua v1.29.1
Date: 2026-10-31
Previous release: v1.29.0
Changed
- Compiled binaries are removed from the repository and its history. Library code is unchanged from v1.29.0. Tags from before this release were rewritten, so GitHub now serves different module contents for 13 of them, and
GOPRIVATEbuilds that pin one of those versions fail theirgo.sumcheck; move to this release.