[ 
https://issues.apache.org/jira/browse/KNOX-3376?focusedWorklogId=1030052&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1030052
 ]

ASF GitHub Bot logged work on KNOX-3376:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 13/Jul/26 11:35
            Start Date: 13/Jul/26 11:35
    Worklog Time Spent: 10m 
      Work Description: smolnar82 opened a new pull request, #1304:
URL: https://github.com/apache/knox/pull/1304

   [KNOX-3376](https://issues.apache.org/jira/browse/KNOX-3376) - Use 
DeafultAliasService in Knox OOTB
   
   ## What changes were proposed in this pull request?
   
   Remove the incomplete OOTB configuration of `RemoteAliasService` from 
`gateway-site.xml`.
   
   ## How was this patch tested?
   
   Built and started Knox. Relevant logs:
   ```
   2026-07-13 13:33:48,889  INFO  knox.gateway 
(AbstractServiceFactory.java:logServiceUsage(105)) - Using default 
implementation for AliasService
   ...
   2026-07-13 13:33:51,812  INFO  knox.gateway 
(AbstractGatewayServices.java:start(60)) - Starting service: 
org.apache.knox.gateway.services.security.impl.DefaultAliasService
   ```
   
   ## Integration Tests
   N/A
   
   ## UI changes
   N/A




Issue Time Tracking
-------------------

            Worklog Id:     (was: 1030052)
    Remaining Estimate: 0h
            Time Spent: 10m

> 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
>            Priority: Major
>             Fix For: 3.0.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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)

Reply via email to