Sandor Molnar created KNOX-3376:
-----------------------------------
Summary: Use DefultAliasService OOTB
Key: KNOX-3376
URL: https://issues.apache.org/jira/browse/KNOX-3376
Project: Apache Knox
Issue Type: Improvement
Components: Server
Reporter: Sandor Molnar
Assignee: Sandor Molnar
Fix For: 3.0.0
Currently, the following config is set in {{gateway-site.xml}}:
{noformat}
<property>
<name>gateway.service.alias.impl</name>
<value>org.apache.knox.gateway.services.security.impl.RemoteAliasService</value>
</property>
{noformat}
Since there is no other {{remote}} config defined, Knox falls back to
`ZooKeeper`. No ZK-related configs either -> just an unnecessary round in
remote alias provider every time that checks if remote exists (not) then turn
to local.
Relevant logs:
{noformat}
2026-07-10 22:14:45,225 INFO knox.gateway
(AbstractServiceFactory.java:logServiceUsage(105)) - Using
org.apache.knox.gateway.services.security.impl.RemoteAliasService
implementation for AliasService
2026-07-10 22:14:45,227 INFO knox.gateway (RemoteAliasService.java:init(291))
- Remote Alias Service enabled
2026-07-10 22:14:45,228 WARN knox.gateway
(ZookeeperRemoteAliasService.java:init(411)) - There is no registry client
defined for remote configuration monitoring.
{noformat}
Given all these, it doesn't make sense to default to the remote alias service
implementation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
