Skip to content

[Bug]: OPCUA is not authenticating with Basic256Sha256 certificate #2127

Open
@rmehra76-git

Description

@rmehra76-git

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//:?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//:?security-policy=Basic256Sha256&message-security=SIGN_ENCRYPT&key-store-type=pkcs12&key-store-file=/c///.p12&key-store-password=

This gives an error that "remote host closed connection"

I'm using windows machine to connect is this path in correct format /c///.p12
My actual windows path is c:<maindir><subdir><filename>.p12

Option 3:
opcua:tcp//:?security-policy=Basic256Sha256&message-security=SIGN_ENCRYPT&server-certificate-file=/c///.der

This is also giving the same error as 2

Version

0.12

Programming Languages

  • plc4c
  • plc4go
  • plc4j
  • plc4net
  • plc4py

Protocols

  • AB-Ethernet
  • ADS /AMS
  • BACnet/IP
  • C-Bus
  • CANopen
  • EtherNet/IP
  • Firmata
  • IEC-69870
  • KNXnet/IP
  • Modbus
  • OPC-UA
  • Profinet
  • S7
  • S7-light

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions