[
https://issues.apache.org/jira/browse/KNOX-2732?focusedWorklogId=760395&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-760395
]
ASF GitHub Bot logged work on KNOX-2732:
----------------------------------------
Author: ASF GitHub Bot
Created on: 21/Apr/22 20:19
Start Date: 21/Apr/22 20:19
Worklog Time Spent: 10m
Work Description: pzampino commented on code in PR #560:
URL: https://github.com/apache/knox/pull/560#discussion_r855560683
##########
gateway-provider-security-jwt/src/main/java/org/apache/knox/gateway/provider/federation/jwt/filter/JWTAuthCodeAssertionFilter.java:
##########
@@ -55,6 +57,10 @@ public void init( FilterConfig filterConfig ) throws
ServletException {
GatewayServices services = (GatewayServices)
filterConfig.getServletContext().getAttribute(GatewayServices.GATEWAY_SERVICES_ATTRIBUTE);
authority = services.getService(ServiceType.TOKEN_SERVICE);
sr = services.getService(ServiceType.SERVICE_REGISTRY_SERVICE);
+
+ this.tokenIssuer =
filterConfig.getInitParameter(JWTAccessTokenAssertionFilter.ISSUER) != null
+ ?
filterConfig.getInitParameter(JWTAccessTokenAssertionFilter.ISSUER)
Review Comment:
I can't imagine a case for multiple issuers. In that case, we would use
multiple topologies IMO.
Issue Time Tracking
-------------------
Worklog Id: (was: 760395)
Time Spent: 1h 20m (was: 1h 10m)
> Issuer claim in Knox JWTs should be configurable
> ------------------------------------------------
>
> Key: KNOX-2732
> URL: https://issues.apache.org/jira/browse/KNOX-2732
> Project: Apache Knox
> Issue Type: Improvement
> Components: Server
> Affects Versions: 1.6.0
> Reporter: Philip Zampino
> Assignee: Attila Magyar
> Priority: Major
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Currently, the issuer claim in JWTs issued by Knox is always "KNOXSSO". This
> value should be configurable via a KNOXTOKEN service param in the topology.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
