Apache StreamPipes version
dev (current development state)
Affected StreamPipes components
UI
What happened?
Description
In the OPC UA certificate management UI (Settings → Certificates), the overview list displays the issuing CA's issuerDn (e.g. CN=My Intermediate CA,O=My Organization,C=DE) rather than the certificate's own subjectDn.
Problem
When multiple servers are signed by the same intermediate/root CA, they all show identical information in this list, making it impossible to distinguish individual server certificates at a glance - even though the detail view (opened per certificate) already has everything needed to tell them apart.
Suggestion
Show subjectDn as the primary identifier in the list instead of issuerDn. Additionally showing the URI entry from subjectAlternativeNames (the OPC UA ApplicationUri) would help too, since that's the identity that actually matters for OPC UA connections - subjectDn's Common Name is often arbitrary free text, while the ApplicationUri is what's configured in the connecting application.
Both fields are already present in the per-certificate detail view, so this would just be surfacing existing data one level higher, in the list itself.
How to reproduce?
No response
Expected behavior
No response
Additional technical information
No response
Are you willing to submit a PR?
None
Apache StreamPipes version
dev (current development state)
Affected StreamPipes components
UI
What happened?
Description
In the OPC UA certificate management UI (Settings → Certificates), the overview list displays the issuing CA's
issuerDn(e.g.CN=My Intermediate CA,O=My Organization,C=DE) rather than the certificate's ownsubjectDn.Problem
When multiple servers are signed by the same intermediate/root CA, they all show identical information in this list, making it impossible to distinguish individual server certificates at a glance - even though the detail view (opened per certificate) already has everything needed to tell them apart.
Suggestion
Show
subjectDnas the primary identifier in the list instead ofissuerDn. Additionally showing theURIentry fromsubjectAlternativeNames(the OPC UA ApplicationUri) would help too, since that's the identity that actually matters for OPC UA connections -subjectDn's Common Name is often arbitrary free text, while the ApplicationUri is what's configured in the connecting application.Both fields are already present in the per-certificate detail view, so this would just be surfacing existing data one level higher, in the list itself.
How to reproduce?
No response
Expected behavior
No response
Additional technical information
No response
Are you willing to submit a PR?
None