[ 
https://issues.apache.org/jira/browse/KNOX-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18115042#comment-18115042
 ] 

ASF subversion and git services commented on KNOX-3445:
-------------------------------------------------------

Commit 739011b0c16e44697f09dfcbccc2ea1e7c7258aa in knox's branch 
refs/heads/master from hanicz
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=739011b0c ]

KNOX-3445: KnoxIDF admin service stays disabled (Empty stub) when KNOXIDF_ADMIN 
topology is hot-deployed after gateway startup (#1394)

* KNOX-3445: Default KnoxIDF service factories to H2 instead of topology-gated 
Empty stubs

* KNOX-3445: New tests for JDBC impls

> KnoxIDF admin service stays disabled (Empty stub) when KNOXIDF_ADMIN topology 
> is hot-deployed after gateway startup
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: KNOX-3445
>                 URL: https://issues.apache.org/jira/browse/KNOX-3445
>             Project: Apache Knox
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: 3.1.0
>            Reporter: Tamás Hanicz
>            Priority: Blocker
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> TrustedOidcIssuerServiceFactory / DelegationPolicyServiceFactory decide 
> between the real backend (JDBC/H2) and EmptyTrustedOidcIssuerService once, at 
> gateway startup, via isKnoxIdfEnabledInAnyTopology(). If no 
> KNOXIDF/KNOXIDF_ADMIN topology exists at that moment, the no-op stub is 
> selected and kept for the life of the JVM.
> When such a topology is deployed after startup (hot reload), the REST 
> resources start serving, but the backing service is still the stub. Result:
> - GET .../trusted-oidc-issuers → [] (Empty.list())
> - POST .../trusted-oidc-issuers → Empty.register() throws 
> UnsupportedOperationException → caught as generic 500 storage_error "Failed 
> to register issuer", with no error logged.
> The 500/storage_error is misleading (implies a DB failure) and there's no log 
> pointing to the real cause. Also there are no error logs.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to