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

Incorporate Bearer Authentication. #21

Closed
davinchia opened this issue Mar 9, 2020 · 2 comments
Closed

Incorporate Bearer Authentication. #21

davinchia opened this issue Mar 9, 2020 · 2 comments

Comments

@davinchia
Copy link

davinchia commented Mar 9, 2020

Generated swagger should incorporate bearer authentication to fully reflect our use of JWT as an authentication method.

One possible way to do this is to turn this on by default for all routes, and expose a excludes method to pardon certain routes.

See https://swagger.io/docs/specification/authentication/bearer-authentication/ for swagger specific detail.

@liveandrew
Copy link

let's chat through the changes, would be great to have to add it! i'm presuming this is only something we need for external apis?

@davinchia
Copy link
Author

davinchia commented Mar 11, 2020

Cool! From an authentication/authorisation viewpoint, the way we expose our APIs should not change from LiveRamp-internal/LiveRamp-external. That is, in general, all APIs require bearer authorisation to work. (At least that's how Nexus has envisioned this, and I agree with). E.g. the direct-to-dist api requires this even though Select is LiveRamp-internal.

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

No branches or pull requests

3 participants