[ 
https://issues.apache.org/jira/browse/KNOX-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sandeep More updated KNOX-3040:
-------------------------------
    Description: 
Currently we can only have one way to validate JWT token either 
# Using JWKS endpoint 
# Using PEM
# Using the signing-key
We should be able to support multiple verifications together. 

This is an example configuration

{code:java}
<provider>
            <role>federation</role>
            <name>JWTProvider</name>
            <enabled>true</enabled>
            <param>
                <name>knox.token.use.cookie</name>
                <value>true</value>
            </param>
                        
            <param>
                <name>knox.token.jwks.url</name>
                <value>https://my.idp.com/oauth/.wellknown</value>
            </param>


            <param>
                <name>knox.token.verification.pem</name>
                
<value>MIIDaDCCAlCgAwIBAgIJAKFjn6W+gdAXMA0GCSqGSIb3DQEBBQUAMF8xCzAJBgNVBAYTAlVTMQ0wC...</value>
            </param>

            <param>
                <name>jwt.expected.issuer</name>
                <value>https://my.idp.com/</value>
            </param>

            <param>
                <name>knox.token.use.cookie</name>
                <value>true</value>
            </param>
        </provider>
{code}


  was:
Currently we can only have one way to validate JWT token either 
# Using JWKS endpoint 
# Using PEM
# Using the signing-key
We should be able to support multiple verifications together. 


> Support multiple ways to verify JWT tokens
> ------------------------------------------
>
>                 Key: KNOX-3040
>                 URL: https://issues.apache.org/jira/browse/KNOX-3040
>             Project: Apache Knox
>          Issue Type: Bug
>            Reporter: Sandeep More
>            Assignee: Sandeep More
>            Priority: Major
>             Fix For: 2.1.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Currently we can only have one way to validate JWT token either 
> # Using JWKS endpoint 
> # Using PEM
> # Using the signing-key
> We should be able to support multiple verifications together. 
> This is an example configuration
> {code:java}
> <provider>
>             <role>federation</role>
>             <name>JWTProvider</name>
>             <enabled>true</enabled>
>             <param>
>                 <name>knox.token.use.cookie</name>
>                 <value>true</value>
>             </param>
>                       
>             <param>
>                 <name>knox.token.jwks.url</name>
>                 <value>https://my.idp.com/oauth/.wellknown</value>
>             </param>
>             <param>
>                 <name>knox.token.verification.pem</name>
>                 
> <value>MIIDaDCCAlCgAwIBAgIJAKFjn6W+gdAXMA0GCSqGSIb3DQEBBQUAMF8xCzAJBgNVBAYTAlVTMQ0wC...</value>
>             </param>
>             <param>
>                 <name>jwt.expected.issuer</name>
>                 <value>https://my.idp.com/</value>
>             </param>
>             <param>
>                 <name>knox.token.use.cookie</name>
>                 <value>true</value>
>             </param>
>         </provider>
> {code}



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

Reply via email to