[
https://issues.apache.org/jira/browse/NIFI-7161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Villard resolved NIFI-7161.
----------------------------------
Resolution: Not A Problem
This works as designed. When using a load balancer in front of NiFi, session
affinity should be used so that a client is always redirected to the same node
(unless this node goes down). The token is local to the node where it has been
obtained.
Will close the issue but please feel free to re-open if needed or if I
misunderstood the situation.
> Issue with token replication in the cluster.
> --------------------------------------------
>
> Key: NIFI-7161
> URL: https://issues.apache.org/jira/browse/NIFI-7161
> Project: Apache NiFi
> Issue Type: Bug
> Components: Security
> Affects Versions: 1.10.0
> Reporter: Pradeep
> Priority: Major
>
> *Scenario :* A cluster has been setup using the three node of the nifi. LDAP
> has been been configured. The token has been generated and used to access the
> api. In addition, the load balancer has been integrated with cluster with
> round-robin algorithm.
> *Problem :* While reusing the token with subsequent api call, it get failed.
> Due to invalid token.
> *Observation :* The load balancer using the round-robin algorithm where the
> subsequent call has been forwarded the other nifi node in the cluster. Hence,
> the token valid in the one nifi node is not valid to other node in the
> cluster.
> *Logs : _"_*_Unable to validate the access token."_
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
