rmehra76-git opened a new issue, #2127:
URL: https://github.com/apache/plc4x/issues/2127

   ### What happened?
   
   Hi,
   I'm using using nifi and PLC4X under the hood. I have tried multiple options 
to connect to kepware using certificates 
   
   **_Option1: self signed cert from Apache_** 
   The PLC4X is sending a self signed certificate when I send the following 
connectionstring
   
opcua:tcp//<myservername>:<port>?security-policy=Basic256Sha256&message-security=SIGN_ENCRYPT
   
   This creates a sha1RSA certificate on my kepserver which is not compatible 
with my organization security standard 
   
   Option 2: Specify the keystore
   
opcua:tcp//<myservername>:<port>?security-policy=Basic256Sha256&message-security=SIGN_ENCRYPT&key-store-type=pkcs12&key-store-file=/c/<maindir>/<subdir>/<filename>.p12&key-store-password=<pwd>
   
   This gives an error that "remote host closed connection"
   
   I'm using windows machine to connect is this path in correct format 
/c/<maindir>/<subdir>/<filename>.p12
   My actual windows path is c:\<maindir>\<subdir>\<filename>.p12
   
   
   Option 3:
   
opcua:tcp//<myservername>:<port>?security-policy=Basic256Sha256&message-security=SIGN_ENCRYPT&server-certificate-file=/c/<maindir>/<subdir>/<certificate>.der
   
   This is also giving the same error as 2
   
   
   
   ### Version
   
   0.13
   
   ### Programming Languages
   
   - [ ] plc4c
   - [ ] plc4go
   - [x] plc4j
   - [ ] plc4net
   - [ ] plc4py
   
   ### Protocols
   
   - [ ] AB-Ethernet
   - [ ] ADS /AMS
   - [ ] BACnet/IP
   - [ ] C-Bus
   - [ ] CANopen
   - [ ] EtherNet/IP
   - [ ] Firmata
   - [ ] IEC-69870
   - [ ] KNXnet/IP
   - [ ] Modbus
   - [x] OPC-UA
   - [ ] Profinet
   - [ ] S7
   - [ ] S7-light


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@plc4x.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to