[MGNLRESTCL-221] securitySchemes REST client does not get latest Password value Created: 31/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: Sergio Marino Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
dependency
depends upon PSWDMNGR-38 securitySchemes REST client does not ... Closed
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
Epic Link: Password manager maintenance
Team: DeveloperX
Work Started:

 Description   

Steps to reproduce

  1. Install Magnolia (mgnl jumpstart and unzip the light-module provided, myLm.zip), I will refer this project as Magnolia from now on. Then start magnolia (mgnl start), from Passwords app create a new password (whatever value). Keep the <uuid> for step 4.
  2. Start up Spring Boot project attached, unzip from prueba.zip.
  3. From Magnolia, go to light-modules->myLm->restClient->prueba.yaml and update lines 9, 10 and 21 (lines that have the password uuid) with the password <uuid> you got from step 1.
  4. From Magnolia, create a new page from pages-app using the template "my-homepage" (that template performs a call to the Spring boot project).
  5. Once you render the page go to the console of the Spring Boot project (step 2), you will see from the console the passwords being sent for the api_key and Authorization header (this header is created when using basic securitySchemes).
  6. From Magnolia, go again to the passwords app and update the password you created at step 1 with a new value (different value from step 1).
  7. From Magnolia refresh the page you created at step 4 again.
  8. Go to Spring boot project console. You will see printed the new updated password for the header api_key, however the Authorization header keeps having the old value.

.. Logs, screenshots, gifs...

Expected results

 At step 8, since the api_key header has its value updated, Authorization header should also print the new value.

Actual results

Authorization header print the old value.

Workaround

Development notes

Security scheme gets the latest password, unfortunately, it is not reloaded after a password change. There is a new functionality in the password manager for m6.2 that allows registering on change listener. For m6.3 there is already on change listener integrated in data source and can be used. 


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