Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom JWTGenerator [apim.jwt.generator_imp] setting is ignored #8612

Closed
kishiguro opened this issue May 30, 2020 · 1 comment
Closed

Custom JWTGenerator [apim.jwt.generator_imp] setting is ignored #8612

kishiguro opened this issue May 30, 2020 · 1 comment

Comments

@kishiguro
Copy link

Description:

Even if we configure Custom JWTGenerator in [apim.jwt.generator_imp], the setting is completely ignored.

Steps to reproduce:

Set generator_impl config at repository/conf/deployment.toml

[apim.jwt]
enable = true
encoding = "base64"
generator_impl = "org.wso2.custom.TokenGenerator.CustomTokenGenerator"
claim_dialect = "http://wso2.org/claimsx"
header = "X-JWT-Assertion"
signing_algorithm = "SHA256withRSA"
enable_user_claims = true
claims_extractor_impl = "org.wso2.carbon.apimgt.impl.token.DefaultClaimsRetriever"

The CustomTokenGenerator https://github.com/Senthuran100/CustomJWTGenerator is used. We believe somewhere between carbon-apimgt v6.5.437 and v6.6.10 this bug is introduced.

Affected Product Version:

WSO2 API Manager 3.1.0-Alpha and after has the issue. WSO2 API Manager 3.1.0-M5 and previous version does not have the issue. In carbon-apimgt, v6.5.437 is ok, but v6.6.10 has the issue.

Environment details (with versions):

  • OS: Mac OS 10.15.5 & Ubuntu 18.04
  • Client:
  • Env (Docker/K8s): Native

Optional Fields

Related Issues:

Suggested Labels:

Suggested Assignees:

@pttse
Copy link

pttse commented Aug 7, 2020

Just curious is there any quick fix or update for this bug?
Our team now faces the same situation. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants