[
https://issues.apache.org/jira/browse/NIFI-9838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Gyori updated NIFI-9838:
------------------------------
Description:
The ListenTCPRecord processor should read the client certificate's Subject and
Issuer DNs and attach their values to the outgoing flowfile as attributes.
This would enable the implementation of authorization logic downstream in the
flow (e.g. using a RouteOnAttribute processor) using those values.
was:
ListenTCPRecord should contain two new properties 'Authorized Subject DN
Pattern' and 'Authorized Issuer DN Pattern' (just like the ListenHTTP
processor) that accept regular expressions that can be applied against the
client certificate's Subject and Issuer DN if secure connection is used.
The processor should also read the client certificate's Subject and Issuer DN
and attach their values to the outgoing flowfile as attributes.
The processor does not need to perform authorization based on the DN values, it
should simply attach the value of the 'Authorized Subject DN Pattern' and
'Authorized Issuer DN Pattern' properties as well as the client certificate's
'Subject DN' and 'Issuer DN' to the outgoing flowfiles as attributes thus
enabling the implementation of authorization logic downstream in the flow (e.g.
using a RouteOnAttribute processor).
> ListenTCPRecord should add client certificate's Subject and Issuer DNs to
> flowfiles as attributes
> -------------------------------------------------------------------------------------------------
>
> Key: NIFI-9838
> URL: https://issues.apache.org/jira/browse/NIFI-9838
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
> Reporter: Peter Gyori
> Assignee: Peter Gyori
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The ListenTCPRecord processor should read the client certificate's Subject
> and Issuer DNs and attach their values to the outgoing flowfile as attributes.
> This would enable the implementation of authorization logic downstream in the
> flow (e.g. using a RouteOnAttribute processor) using those values.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
