The 'default' scope missing in the generated access token

[Manasha11]

Description

After updating the APIM 4.1.0 to U2 level 165, and adding the latest libraries (wso2is.key.manager.core-1.4.2.14.jar and wso2is.notification.event.handlers-1.4.2.14.jar) and webapp (keymanager-operations.war) to the IS 5.11.0, the generated JWT token does not contain the 'default' token.

Steps to Reproduce

• Configure APIM 4.1.0.165 with IS 5.11.0 as the Key Manager following [1].
• Copy following JAR files (of IS connector [1]) to the <IS_HOME>/repository/components/dropins directory.

wso2is.key.manager.core-1.4.2.14.jar
wso2is.notification.event.handlers-1.4.2.14.jar

• Copy keymanager-operations.war to the <IS_HOME>/repository/deployment/server/webapps directory.
  Startup APIM and IS servers.
• Generate a JWT token using an application.
• The generated token:
  eyJ4NXQiOiJNVEZsTmprMU56RTNZV0ZsWmpkak16YzROV0U1WmpSbFpXUmpZVFEwTXpJMU1UVTBNamxoWWciLCJraWQiOiJZV0kzWW1NNU1ETTRNR016Tm1FeFpEWTRObVF6T0RGbU5qQTBaRE13TTJKbU1EbGtNR1l4Tm1aaE9XRmlOamRoT0dKa00yTXdZV1poTUdWbE9EWXpOQV9SUzI1NiIsImFsZyI6IlJTMjU2In0.eyJzdWIiOiJhZG1pbiIsImF1dCI6IkFQUExJQ0FUSU9OIiwiYXVkIjoib241ZDVQQmZoallrSEhFaUJhV01QMkY4SktnYSIsIm5iZiI6MTcyOTE2NDE3OSwiYXpwIjoib241ZDVQQmZoallrSEhFaUJhV01QMkY4SktnYSIsImlzcyI6Imh0dHBzOlwvXC9sb2NhbGhvc3Q6OTQ0NFwvb2F1dGgyXC90b2tlbiIsImV4cCI6MTcyOTE2Nzc3OSwiaWF0IjoxNzI5MTY0MTc5LCJqdGkiOiJiN2I1Y2U0MS03ZTA3LTRlODItOGJmYS1mZTEwM2ViMmU1N2YifQ.dbHG1yVtbHD32lsxUXtVD-FdVLPgI7scit97e7X3xUUQ33iwdceUbDVnHuVnH1BoKjk_iuVJ7UB7yITkwOi9fUZjgmhBIzBGCzcS0RVJP4Mf3RymaA1yZ2rCi2pWXxyVsJ6MxJ3sVEI0VUR-rgwZDJnpbMAFGwW4tAo2fgKdSZayZ0IBrFr1RnzOj4Kb1XEPd7OpdSOptJs4el-1eWGHAiRifu3-d-7ulQLFs4xn_y5BP4fgIgrc_gquZtTVW8oTKD2HB81syUNwI66rpBrVuE2Ownr0l02ZQDSuQ7hCH8xkVKScKrt3FA2fO5zLNZWQrGBXRofd2Crkjo-dzsT7ww

Note that it does not contain the 'default' scope.

Affected Component

APIM

Version

4.1.0

Environment Details (with versions)

No response

Relevant Log Output

No response

Related Issues

No response

Suggested Labels

No response