Introduce JWT Access Token Attributes

[shashimalcse]

Purpose

$subject

Related Issues

• Selective JWT Access Token Claims Handling product-is#20880

New Applications:

Existing Application (Upgrade path):

Related PRs

• N/A

Checklist

• e2e cypress tests locally verified. (for internal contributers)

• Manual test round performed and verified.

• UX/UI review done on the final implementation.

• Documentation provided. (Add links if there are any)

• Relevant backend changes deployed and verified

• Unit tests provided. (Add links if there are any)

• Integration tests provided. (Add links if there are any)

Security checks

• Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines
• Ran FindSecurityBugs plugin and verified report
• Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets

[pavinduLakshan]

Let's add changeset and fix eslint issues

[Achintha444]

Increase the padding between the token type and the warning message

[shashimalcse]

Increase the padding between the token type and the warning message

fixed

[wso2-jenkins-bot]

🦋 Changeset detected

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

[himeshsiriwardana]

The message, as discussed, is now clear. But the text will need to be properly formatted to improve readability. can we separate the text into sections.

previous behavior
new behavior
important info

Just a line separator between these points will suffice.

furthermore,

• User Attributes is the section. not User.
• Previously, all attributes marked as requested in the application's User Attributes section, referred to as requested attributes below, were ...