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

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

                Author: ASF GitHub Bot
            Created on: 30/Sep/26 17:24
            Start Date: 30/Sep/26 17:24
    Worklog Time Spent: 10m 
      Work Description: moresandeep opened a new pull request, #1437:
URL: https://github.com/apache/knox/pull/1437

   
   [KNOX-3498](https://issues.apache.org/jira/browse/KNOX-3498) - In cases of 
failures with OIDC issuer discovery url containing IP addresses log a proper 
error and warn message.
   
   NOTE: Claude Code (Opus 5.5) was used to assist with debugging of the issue 
and helping out with the code. The PR was inspected and reviewed by me. 
   
   ## What changes were proposed in this pull request?
   
   Add a proper error messages so we don't chase after wrong issues.
   
   ## How was this patch tested?
   
   Patch was tested locally.
   
   ## Integration Tests
   N/A
   
   




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

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

> OIDC issuer discovery url with IP breaks when FIPS enabled.
> -----------------------------------------------------------
>
>                 Key: KNOX-3498
>                 URL: https://issues.apache.org/jira/browse/KNOX-3498
>             Project: Apache Knox
>          Issue Type: Bug
>          Components: Server
>            Reporter: Sandeep More
>            Assignee: Sandeep More
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> A trusted OIDC issuer whose discovery url has IP (used in`jwks_uri`) breaks 
> with BouncyCastle FIPS, the failure looks like a missing CA which is 
> misleading. 
>  
> For KnoxIDF, registering a trusted OIDC issuer whose discovery document 
> advertises `jwks_uri` as an IP makes token exchange fail, and the reported
> error is looks similar to trust-store misconfiguration. Example is in k8s
> : kube-apiserver advertises an IP by default, e.g.
>     "jwks_uri": "https://10.83.4.208:6443/openid/v1/jwks";
>  
> *Workaround:*
> 1. Knox config: 
> Move the issuer onto the static verification route, which accepts an explicit
> JWKS URL list, and give it the hostname form of the endpoint:
>     <param><name>jwt.expected.issuer</name>
>       
> <value>KNOXSSO,https://kubernetes.default.svc.cluster.local</value></param>
>     <param><name>knox.token.jwks.urls</name>
>       
> <value>https://knox.example.com/gateway/knox-token/knoxtoken/api/v1/jwks.json,
>              
> https://kubernetes.default.svc.cluster.local/openid/v1/jwks</value></param>
> 2. K8S Config 
> Alternatively fix it at the source with kube-apiserver
> `--service-account-jwks-uri=https://kubernetes.default.svc.cluster.local/openid/v1/jwks`.



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

Reply via email to