Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Port - 6081 Dev Studio - PROD mid access (via access code) and API key generation in dev studio CHF-1192 #511

Closed
ChithraCH opened this issue Sep 6, 2023 · 3 comments
Assignees
Labels
CommerceHub Label representing CommerceHub enhancement New feature or request Priority - High stale

Comments

@ChithraCH
Copy link

ChithraCH commented Sep 6, 2023

https://jira.onefiserv.net/browse/CHF-1192

Context

PROD mid access (via access code) and API key generation in dev studio

Solution

Requirement:

  1. Developer shall be allowed to key in and verify the access code received for prod MIDs
  2. Developer shall be allowed to create API key for single/multiple prod MIDs
  3. Developer shall be allowed to clone prod mid to sandbox mid.
  4. This sandbox mid will be created under same client id (in lower environment)
  5. Developer shall be able to see the prod MID config using "view" option (read only mode)
  6. Developer shall not be allowed to generate prod API keys for prod MIDs unless it has gone through successful certification for respective client and developer.
  7. Having said that, dev studio needs to provision an option for Fiserv certification team (Ramon’s team) to enable prod API key generation option at a developer and client ID level.
  8. Once prod API key option is generated, dev studio to ensure that developer can generate prod API keys for the MIDs configured under respective client ID (enabled by Ramon’s team) only.

For Example :

  1. THDPROD and THDSTAGE is client id in prod and stage region respectively.
  2. Developer is provided with an access code for sharing THDPRODMID1, THDPRODMID2 from prod region.
  3. Post successful verification of access code developer can see THDPRODMID1, THDPRODMID2 in dev studio.
  4. If developer is cloning THDPRODMID1 to THDSANDBOXMID1 (new mid) then
    THDSANDBOXMID1 shall get created under THDSTAGE

Alternatives

N/A

Additional Context

Scenarios:

Below are the scenarios covered for more understanding. As per current approach,

  1. As soon as a contract is in place and either an E2E or Prod MID is created, merchant admin can provide access of these MIDs to developer using access code functionality.
  2. Once developer gets an access to E2E or Prod MID, developer is allowed to generate API keys (E2E / Prod) against it and start using it.
  3. Currently, we don’t have any mechanism in place to certify merchant automatically, we need to make sure that developer is not allowed to generate API keys for prod MIDs.
  4. To ensure same, dev studio needs to support an intermediatory solution using which certification team can enable option of generating prod API keys in dev studio.

Update 03/27 - 

Update with reference to quick chat (teams) with MP team. Marketplace is already supporting below functionality,

Send access code for prod MIDs
Create a sandbox mid by cloning prod mid

Dev Studio needs to ensure this functionality in QA stage. 

Region

Commerce Hub

@ChithraCH ChithraCH added the enhancement New feature or request label Sep 6, 2023
@sfiserv sfiserv self-assigned this Sep 8, 2023
@sfiserv sfiserv added the CommerceHub Label representing CommerceHub label Sep 8, 2023
@sfiserv sfiserv added this to the Future Enhancements milestone Sep 21, 2023
@ChithraCH
Copy link
Author

Feature is available in Prod. Please do one round of testing before closing this issue.

Copy link

stale bot commented Nov 26, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Nov 26, 2023
@sfiserv sfiserv removed the stale label Nov 27, 2023
Copy link

stale bot commented Jan 26, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jan 26, 2024
@sfiserv sfiserv removed the stale label Jan 26, 2024
@sfiserv sfiserv added the stale label Mar 2, 2024
@sfiserv sfiserv closed this as completed Mar 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CommerceHub Label representing CommerceHub enhancement New feature or request Priority - High stale
Projects
None yet
Development

No branches or pull requests

2 participants