[
https://issues.apache.org/jira/browse/NIFI-9397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-9397:
-----------------------------------
Fix Version/s: 1.16.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Add custom authorization to JettyWebSocketClient
> ------------------------------------------------
>
> Key: NIFI-9397
> URL: https://issues.apache.org/jira/browse/NIFI-9397
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Simon Bence
> Assignee: Simon Bence
> Priority: Major
> Fix For: 1.16.0
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> Adding secure property which -in case of being set- is used as the value for
> Authorization header. By this, services using different kind of auth (like
> api key) can be reached using the controller service.
> -Adding sensitive dynamic property support in the same manner it was
> implemented in the
> [DBCPConnectionPool|https://issues.apache.org/jira/browse/NIFI-8047]- (This
> approach is not sercure as kindly highlighted by [~exceptionfactory])
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
