[
https://issues.apache.org/jira/browse/NIFI-13602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Gilman updated NIFI-13602:
-------------------------------
Fix Version/s: 2.0.0-M5
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Logout Link not shown for Clustered Deployments
> -----------------------------------------------
>
> Key: NIFI-13602
> URL: https://issues.apache.org/jira/browse/NIFI-13602
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 2.0.0-M4
> Reporter: David Handermann
> Assignee: David Handermann
> Priority: Minor
> Fix For: 2.0.0-M5
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> NiFi 2.0.0-M4 included changes to the user interface and REST API that added
> a logoutSupported property to the current user response object. The user
> interface checks the logoutSupported property to determine whether to show
> the logout link. The REST API derives the logoutSupported status based on the
> type of authentication presented for the HTTP request, looking for the
> Application Bearer Token to enable the logoutSupported property.
> In clustered deployments, the cluster node receiving the initial HTTP request
> replicates it to other nodes and merges the responses. Replicated requests
> pass the initial authenticated user in a custom HTTP request header, as
> opposed to the cookie header containing the Application Bearer Token from the
> browser. As a result of merging responses, the logoutSupported status is
> always set to false, regardless of the authentication method. This behavior
> should be changed to set logoutSupported to true if any of the current user
> entities have a true value.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
