-
Notifications
You must be signed in to change notification settings - Fork 8.5k
Upgrade Assistant should work with token based authentication #72014
Copy link
Copy link
Closed
Labels
Feature:Security/AuthenticationPlatform Security - AuthenticationPlatform Security - AuthenticationFeature:Upgrade AssistantTeam:Kibana ManagementDev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more t//Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more t//Team:SecurityPlatform Security: Auth, Users, Roles, Spaces, Audit Logging, etc t//Platform Security: Auth, Users, Roles, Spaces, Audit Logging, etc t//blockedenhancementNew value added to drive a business resultNew value added to drive a business resultimpact:lowAddressing this issue will have a low level of impact on the quality/strength of our product.Addressing this issue will have a low level of impact on the quality/strength of our product.loe:mediumMedium Level of EffortMedium Level of Effort
Metadata
Metadata
Assignees
Labels
Feature:Security/AuthenticationPlatform Security - AuthenticationPlatform Security - AuthenticationFeature:Upgrade AssistantTeam:Kibana ManagementDev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more t//Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more t//Team:SecurityPlatform Security: Auth, Users, Roles, Spaces, Audit Logging, etc t//Platform Security: Auth, Users, Roles, Spaces, Audit Logging, etc t//blockedenhancementNew value added to drive a business resultNew value added to drive a business resultimpact:lowAddressing this issue will have a low level of impact on the quality/strength of our product.Addressing this issue will have a low level of impact on the quality/strength of our product.loe:mediumMedium Level of EffortMedium Level of Effort
Type
Fields
Give feedbackNo fields configured for issues without a type.
Upon receiving a request to reindex, Upgrade Assistant (UA) stores the requester's credentials in memory and uses those credentials when updating saved objects and issuing requests for other reindexing related operations.
In a token-based authentication mechanism these tokens have an expiration time that could expire before reindexing work completes causing the task to stall. With state of reindexing tracked inside of saved objects this should be recoverable but the ideal would be that no recovery is required.
At the moment there is no simple way to refresh the auth token on behalf of the requester.
See https://github.com/elastic/kibana-team/issues/1331 for a similar issue and a proposed solution.