Closed vishmi49 closed 7 months ago
@vishmi49 did you add all the configurations mentioned in https://apim.docs.wso2.com/en/4.3.0/install-and-setup/setup/security/securing-api-m-web-portals/#enable-jwt-for-web-portals? From the reproducing steps i could see only one config
Hi All,
The reproducing steps are as follows.
[oauth]
add_tenant_domain_to_access_token = true
[oauth.token_persistence] enable=false
[oauth.revoked_token_headers_in_response] enable=false
[[oauth.extensions.token_types]] name = "JWT" issuer = "org.wso2.is.key.manager.tokenpersistence.issuer.ExtendedJWTTokenIssuer"
[transport.https.properties] maxHttpHeaderSize = "12288"
[apim.oauth_config] enable_jwt_for_portals = true
7. Restart the server.
8. Access the Devportal and click on carbon.super from the Tenant selection.
9. Login to the developer portal using the wso2.com tenant's credentials.
10. You will observer the errors mentioned in the description above.
However this is the expected behaviour because the SPs were created before enabling the token persistence configuration. To fix it, we need to follow the steps in the documentation [1] for an existing deployment.
As this is not a bug, I will close the issue.
[1] https://apim.docs.wso2.com/en/4.3.0/install-and-setup/setup/security/securing-api-m-web-portals/#enable-jwt-for-web-portals
Thanks,
Tharika.
Description
Issuer is not set as JWT for service providers when the config is enabled. If the token persistence configs are enabled with this feature, users cannot login to portals if a tenant user tries to login to the devportal of super tenant.
Publisher portal
Steps to Reproduce
Prerequisites
[apim.oauth_config]
enable_jwt_for_portals = true
Affected Component
APIM
Version
4.3.0
Environment Details (with versions)
No response
Relevant Log Output
Related Issues
No response
Suggested Labels
No response