[ECOMMERCE-137] Credentials and sensitive information should be stored in PasswordManager Created: 18/Feb/19  Updated: 15/Mar/19  Resolved: 05/Mar/19

Status: Closed
Project: E-commerce
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0

Type: Improvement Priority: Neutral
Reporter: Ilgun Ilgun Assignee: Trung Luu
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 3d 2.5h
Original Estimate: Not Specified

Issue Links:
causality
is causing ECOMMERCE-160 Remove version handler class for encr... Closed
relation
is related to ECOMMERCE-121 DOC: Final pass on installation & con... 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)
Documentation update required:
Yes
Date of First Response:
Epic Link: Configure my e-commerce connection
Sprint: Add-Ons 6
Story Points: 3

 Description   

Currently we store our passwords and sensitive information in the plain String format. However, we should be rather using passwordManager for that capabilities. In our definitions, we should simply refer to passwordManager 'path' and system should automatically pick the credentials from there. 

Acceptance Criteria:

  • Password (Magento) and ClientSecret (commerceTools) are stored in the PasswordManager
  • Definitions are accepting 'path' which refers to password manager
  • System picks up those password automatically from PasswordManager


 Comments   
Comment by Trung Luu [ 08/Mar/19 ]

jlegendre ldelnevo ilgun FYI, Incase we set the password value directly in yaml instead of passwordManger 'path', System will skip to get info from Password Manager app and working normally as old way. Thanks

Comment by Trung Luu [ 08/Mar/19 ]

ilgun Exactly! I have checked that it is the path if it contains '/'

Comment by Julie Legendre [ 12/Mar/19 ]

Thanks trung.luu for the heads up

Generated at Mon Feb 12 01:41:13 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.