Add support for scope validation for Opaque tokens in Websocket and GraphQL subscription APIs

[dushaniw]

Problem

Currently WSO2 API-M 4.2 supports JWT tokens by default. Even though Opaque tokens are deprecated, they are may be cases where users are migrating from older Opaque toke issuer apps. Prior to API-M 4.x, Websocket APIs did not support scopes. However, if a user prior to 4.x, who were using Opaque tokens for Websocket APIs migrate to 4.2, they may get a requirement to add new scopes to old resources and try them with old apps which generate opaque tokens.

Currently we API-M 4.2 does not support scopes for Websocket APIs as well as GraphQL subscriptions (which works on top of Websocket API) with Opaque tokens.

Solution

Support Scope validation for Opaque tokens during Websocket handshake.
Support Scope validation for Opaque tokens during GraphQL subscription operation frame read.

Affected Component

APIM

Version

4.2

Implementation

No response

Related Issues

No response

Suggested Labels

No response

[dushaniw]

fixed in latest