[MGNLRESTCL-220] Bearer security scheme with oauth2 is not persisting authentication token for subsequent calls Created: 23/Oct/23  Updated: 28/Nov/23

Status: Accepted
Project: REST Client
Component/s: None
Affects Version/s: 2.0.4
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Jaroslav Simak Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Epic Link: RESTClient 2024
Team: DeveloperX

 Description   

Steps to reproduce

  • Define rest client which uses oauth2 authentication
  • Define rest client which uses oauth2 client
  • Make multiple calls to the secured service using the client

Expected results

Authentication token is preserved across requests until it expires.

Actual results

Authentication token is not preserved across requests, resulting into oauth2 authentication calls.

Workaround

Development notes

Each call results into making new instance of BearerSecurityScheme where token field is. Token field is thus null every time for every call.


Generated at Mon Feb 12 10:44:20 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.