Adds the option to use security oauth2 authorizationCode flow to the endpoints dealing with QoD sessions, as in some cases they may require user consent, and define scopes for those endpoints.
The new endpoints for QoS Profiles discovery are left with previous security (clientCredentials)
Which issue(s) this PR fixes:
Fixes #161
Special notes for reviewers:
For the short term, I followed the same approach that is used in other WGs with client credentials and 3-legged coexistence, but we will probably need to review the topic in Commonalities or Identity WG, as there is a lack of coherence among different WGs. For example, currently scopes are not defined for OAuth2 Client credentials, in some WGs openidconnect is used instead of oauth2, etc
Changelog input
- Scopes specified and OAuth2 authorizationCode flow added as security mechanism, for operations dealing with QoD sessions
What type of PR is this?
What this PR does / why we need it:
Adds the option to use security oauth2 authorizationCode flow to the endpoints dealing with QoD sessions, as in some cases they may require user consent, and define scopes for those endpoints.
The new endpoints for QoS Profiles discovery are left with previous security (clientCredentials)
Which issue(s) this PR fixes:
Fixes #161
Special notes for reviewers:
For the short term, I followed the same approach that is used in other WGs with client credentials and 3-legged coexistence, but we will probably need to review the topic in Commonalities or Identity WG, as there is a lack of coherence among different WGs. For example, currently scopes are not defined for OAuth2 Client credentials, in some WGs openidconnect is used instead of oauth2, etc
Changelog input
Additional documentation