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

feat(router): Unify Auth in single layer (V2) #7037

Open
AnuthaDev opened this issue Jan 15, 2025 · 0 comments · May be fixed by #7038
Open

feat(router): Unify Auth in single layer (V2) #7037

AnuthaDev opened this issue Jan 15, 2025 · 0 comments · May be fixed by #7038

Comments

@AnuthaDev
Copy link
Contributor

In-efficiency in design

  • Currently we have many types of auth and auth is evaluated in multiple places, with multiple ways.
  • This indeed required multiple approaches and solution needs to be maintained
  • More cognitive load
  • We can’t authenticate a request in one infra component/layer

Unify Auth in single layer

  • Make Authentication header like,
    • authorization: key=value, keyN=valueN
    • Examples:
      • authorization: api-key=
      • authorization: publishable-key=, client-secret=
      • authorization: publishable-key=, ephemeral-key=
      • authorization: jwt=
  • Lineage also should be added in headers, when we can’t inferable from authorization
    • profile_id should be added in headers not in body
    • If api-key not passed or the passed api-key has different scope, then merchant-id also should be passed.
@AnuthaDev AnuthaDev changed the title Unify Auth in single layer (V2) feat(router): Unify Auth in single layer (V2) Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant