[KNOX-1852] Simplify ZookeeperRemoteAliasService and make it generic

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Fix Version/s: 2.1.0
• Component/s: Server
• Assignee: Unassigned
• Reporter: Sandeep More
• Created: 11/Apr/19 18:15
• Updated: 12/Nov/22 22:19

Description

ZookeeperRemoteAliasService class can be made more generic to support future implementations of AliasService that depend on RemoteConfigurationRegistryClient class. Currently, we only have Zookeeper implementation. The purpose of this Jira is to document the following two enhancements to ZookeeperRemoteAliasService class to make it more generic:

1. Change the name to something more generic
2. Move the Zookeeper specific implementation to the class that implements RemoteConfigurationRegistryClient, CuratorClientService in case of Zookeeper service. As an example.
   1. ZookeeperRemoteAliasService.ensureEntry() logic
   2. AUTHENTICATED_USERS_ALL
   3. TYPE

This will be helpful when we decide to implement support for services like consul.

This is a result of offline discussion with [e-mail] about KNOX-1851.

Issue Links

• relates to: KNOX-1851 NPE on startup when Zookeeper Remote Alias Service is configured