Skip to content
This repository has been archived by the owner on Aug 26, 2024. It is now read-only.

Move from API keys to route-based authentication for HTTP gateways #966

Closed
Tracked by #1605
aTeoke opened this issue Aug 11, 2022 · 1 comment · Fixed by #1025
Closed
Tracked by #1605

Move from API keys to route-based authentication for HTTP gateways #966

aTeoke opened this issue Aug 11, 2022 · 1 comment · Fixed by #1025
Assignees
@martinkolenic

Comments

@aTeoke
Copy link

aTeoke commented Aug 11, 2022

Documentation for task #1374
@wkande
Copy link
Member

wkande commented Aug 11, 2022

@aTeoke - Usually the developer that makes the code change follows through on the changes to the docs.

@vponline vponline self-assigned this Aug 31, 2022
@vponline vponline mentioned this issue Sep 12, 2022
Merged
@amarthadan amarthadan assigned martinkolenic and unassigned vponline Sep 13, 2022
@amarthadan amarthadan mentioned this issue Jan 9, 2023
Closed
43 tasks
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@martinkolenic martinkolenic

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Remove gateway apiKeys and add secret UUID path parameter api3dao/old-api3-docs
4 participants
@martinkolenic @wkande @vponline @aTeoke