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

API key request and account set up #9450

Closed
Kaineatthelab opened this issue Oct 12, 2021 · 10 comments
Closed

API key request and account set up #9450

Kaineatthelab opened this issue Oct 12, 2021 · 10 comments
Labels
Milestone

Comments

@Kaineatthelab
Copy link
Collaborator

Kaineatthelab commented Oct 12, 2021

  • How do users request an API key and maintain it, ie: revoke, replace
  • Dependent on Auth and Payment Sandbox set up

Is this available now? or what needs to be done to make it available?

@Kaineatthelab Kaineatthelab added the Dependency To highlight the dependency(intra team, external, third parties) label Oct 12, 2021
@jyoti3286
Copy link
Contributor

For point 2, refer to Sumesh comments in #9161

For account setup: The user will create a premium account. Request access to API Keys via Email. Users accept the API TOS. Then we send the sandbox key and Prod key.

From the Development side, The feature to issue the key is ready from the backend although it hasn't been tested yet. We don't have the feature on the UI to Revoke the keys. That needs to be built.

@Kaineatthelab API items are not on our PI board but are happy to accommodate whatever is required.

@Kaineatthelab
Copy link
Collaborator Author

Thanks @jyoti3286 great! Yes based on these dates we will need image.png

@jinghualicgi
Copy link
Contributor

Please add your planning poker estimate with ZenHub @thorwolpert

@jinghualicgi
Copy link
Contributor

Please add your planning poker estimate with ZenHub @doug-lovett

@jinghualicgi jinghualicgi added this to the Assets - 11.3 milestone Nov 2, 2021
@mstanton1
Copy link
Collaborator

API Key request is covered in 9457. Revoke was built and demo'd by Relationships for Sprint 11.3. I think this can be closed.

@Kaineatthelab @jyoti3286 @thorwolpert @doug-lovett is there actually anything to be done here?

@doug-lovett
Copy link
Collaborator

@Kaineatthelab @mstanton1 @jyoti3286 @thorwolpert
This is working in TEST but not SANDBOX. To verify in SANDBOX we need keycloak and auth SANDBOX instances. The api gateway ppr proxy in the SANDBOX environment will use the client id and secret associated with the api key to request a token from the keycloak SANDBOX instance. So SANDBOX testing is outstanding.

@mstanton1
Copy link
Collaborator

Added 9803 as a blocker. Relationships is almost done that work. @doug-lovett which team will complete this testing when the environment is available?

@doug-lovett
Copy link
Collaborator

@mstanton1 I can as part of updating the SANDBOX gateway configuration. I'll use an api key created by the relationships account set up.

@mstanton1 mstanton1 removed the Dependency To highlight the dependency(intra team, external, third parties) label Nov 18, 2021
@mstanton1
Copy link
Collaborator

Thanks @doug-lovett

@doug-lovett
Copy link
Collaborator

@mstanton1 This ticket can be closed. The gateway config for auth and pay sandbox has been verified.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants