You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
The text was updated successfully, but these errors were encountered:
Description:
Even if we configure Custom JWTGenerator in [apim.jwt.generator_imp], the setting is completely ignored.
Steps to reproduce:
Set
generator_impl
config atrepository/conf/deployment.toml
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):
Optional Fields
Related Issues:
Suggested Labels:
Suggested Assignees:
The text was updated successfully, but these errors were encountered: