|
|
# Configure the certificate validation in your OPC UA server / client
|
|
|
# Configure the certificate validation in S2OPC server / client
|
|
|
|
|
|
In order to activate OPC UA secure communication (integrity and confidentiality) it is necessay to define in which cases a certificate will be valid for your application. A common way to achieve this goal is to define one or several Certificate Authorities (CAs) your application trusts, then all certificates signed by those CAs will be considered valid if security checks pass.
|
|
|
|
|
|
## Reminder on the certificates constraints for OPC UA
|
|
|
|
|
|
### Generate correct certificates for OPC UA usage
|
|
|
|
|
|
TODO: remind key usages / basic constraints to generate valid certificates for OPC UA usage
|
|
|
|
|
|
### Basic examples of valid organization for you certificates
|
|
|
|
|
|
TODO: graphical presentation of self-signed certificate, trusted CA-signed certificate, untrusted CA-signed certificate (trusted), + same with intermediate CA ?
|
|
|
|
|
|
## Configure the certificate validation management in S2OPC
|
|
|
|
|
|
In order to activate secure communication in your S2OPC server or client
|
... | ... | |