# PFC100 OPC UA - CA Certificate handling

**URL:** https://www.wago.community/t/pfc100-opc-ua-ca-certificate-handling/816
**Category:** Hardware and Linux
**Created:** [March 11, 2024, 11:34am UTC](https://www.wago.community/t/pfc100-opc-ua-ca-certificate-handling/816 "2024-03-11T11:34:41Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![WagoKurt](https://sea2.discourse-cdn.com/flex016/user_avatar/www.wago.community/wagokurt/32/11_2.png) [@WagoKurt](https://www.wago.community/u/WagoKurt)
#### Post date: [March 11, 2024, 2:59pm UTC](https://www.wago.community/t/pfc100-opc-ua-ca-certificate-handling/816/2 "2024-03-11T14:59:03Z")

</div>

Hello,  
You might find this thread useful as it is a similar subject.

> [@Tech Note: 3S Runtime with OPC UA Server](https://www.wago.community/t/tech-note-3s-runtime-with-opc-ua-server/305/9):
>
> Does anyone have successfully create his own certificates using openssl and not CODESYS ? The aim is to add the IP in the SubjectAltName, which is not part of the CODESYS generated certificates (only DNS is provided). Sor far here is what I’ve done : Create a ssl.conf file : [req] default\_bits = 3072 serial = 0 default\_md = sha256 distinguished\_name = subject req\_extensions = req\_ext x509\_extensions = req\_ext string\_mask = utf8only prompt = no [req\_ext] basicConstraints = critical, CA:T…

---

_[View the full topic](https://www.wago.community/t/pfc100-opc-ua-ca-certificate-handling/816)._