About OPC UA certificate authentication([Basic Constraints])

Questions regarding the use of the C++ SDK for Server or Client development or integration into customer products ...

Moderator: uasdkcpp

Post Reply
k.maeda
Full Member
Full Member
Posts: 8
Joined: 17 Oct 2017, 09:19

About OPC UA certificate authentication([Basic Constraints])

Post by k.maeda »

Hi SupportTeam,

I'm developing OPC UA Server with UaSDKCpp.
I have question about OPC UA certificate authentication.

I trying to certificate authentication from the next operation.
(1) Put the CA certificate in the TrustedList.
(2) Issue a certificate chained from the CA certificate of (1).
(3) Distribute the certificate of (2) to the client.
(4) The client performs SSL communication using the certificate of (3).

In doing the above,
I would like to prohibit that the certificate forged from the certificate of (3) is authenticated.

For the above reason,
I would like to specify [Basic Constraints]->[pathLenConstraint] to CA certificate.

In Unified Automation,
do you prohibit certificate authentication with a certificate behind the hierarchy specified in [Basic Constraints] -> [pathLenConstraint]?

User avatar
Support Team
Hero Member
Hero Member
Posts: 3068
Joined: 18 Mar 2011, 15:09

Re: About OPC UA certificate authentication([Basic Constrain

Post by Support Team »

Hello k.maeda,

so you want your CA to sign a certificate that can not act as a CA again.
There are multiple settings that need to be considered:

BasicConstraints:
- Subject Type = End Entity (this setting is set to CA for CA certs)
- Path Length Constraint (default = None if you don't want to restrict the length)

Key Usage:
- Off-line CRL Signing (for CA only)
- CRL Signing (for CA only)


So just setting the Path Length Constraint to 1 probably works but isn't really correct. You should also set the Subject Type and Key Usage flags correctly.
Best regards
Unified Automation Support Team

Post Reply