[
https://issues.apache.org/jira/browse/NIFI-7246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17057600#comment-17057600
]
Shreyas KC commented on NIFI-7246:
----------------------------------
[~pvillard] , [~alopresto] I understand it is by design, This implementation is
designed to override the behaviour if the admin chooses to, as it is config
driven with default behaviour to be the older one.
As NiFi is moving to docker/Kubernetes ecosystem, it is primordial we start
designing idempotency in the software design and this is a good start.
> JWT Generated by a node in the cluster is not honored by other nodes in the
> cluster.
> ------------------------------------------------------------------------------------
>
> Key: NIFI-7246
> URL: https://issues.apache.org/jira/browse/NIFI-7246
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework, Security
> Reporter: Shreyas KC
> Priority: Major
>
> In an externally load balanced cluster without sticky session, it is not
> possible to currently share the JWT generated by one node with the rest of
> the nodes in the cluster.
> Hence we need a mechanism where we can introduce static key in the
> nifi.properties in its chosen by the cluster administrator.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
