[ECOMMERCE-196] Magento connector: Allow to configure a access token directly Created: 11/Apr/19  Updated: 16/May/19  Resolved: 26/Apr/19

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

Type: Task Priority: Neutral
Reporter: Adrien Manzoni Assignee: Nguyen Phung Chi
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 1d 7.5h
Original Estimate: Not Specified

Issue Links:
causality
is causing ECOMMERCE-202 DOC: how to configure an access token... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Documentation update required:
Yes
Date of First Response:
Epic Link: E-com improvements 1.0 - 1.1.1 - 1.2
Sprint: Add-Ons 10
Story Points: 5

 Description   

Administrators should be able to choose between providing the user/pwd in clear in the yaml configuration file or providing directly the access_token generated in Magento.

That will allow us to manage the tokens directly in Magento



 Comments   
Comment by Trung Luu [ 25/Apr/19 ]

Hi amanzoni, I have some concerns regarding the access token and user/pwd as below

  1. What's happen if admin put both user/pwd and access token in the yaml configuration?
  2. How about the expired time/date for the access token?

Best regards,
Trung Luu

cc: ldelnevo, ilgun, jlegendre

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