[MGNLRESTCL-89] Securely store API key Created: 24/Oct/19  Updated: 07/Jan/20  Resolved: 07/Jan/20

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

Type: Story Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLRESTCL-44 Securely configure authentication inf... Closed
supersession
is superseded by MGNLRESTCL-113 Hide sensitive information from the r... 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)
Date of First Response:
Epic Link: Declarative REST clients

 Description   

As a developer, I want to use values stored in the Password Manager in my REST calls, so that I can connect to APIs but not expose my API keys or secrets.

Acceptance criteria

  • I can use values from the password manager 
  • In a header, parameter, path or body of REST call

Context

Many API's expect a text API key (sometimes called a secret or an API token) to be provided somewhere in the REST call. 

For example: 
http://api.openweathermap.org/data/2.5/forecast?q=London,us&APPID=11c86e6e92231833a10604185a855418

Notes

This is a follow to the work done in MGNLRESTCL-44, that ticket allows developer to access values from password manager - but only in the specific cases of basic and bearer based authentication.

 

 

 


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