Hey infosec twitter. I have an API that's protected with bearer auth. No cookies anywhere. Can I 'Access-Control-Allow-Origin: *' safely?
It's actually a serious question. And the answer of course doesn't help, because we need the auth header for auth.
-
-
sry then^^ difficult to tell as it highly depends how your bearer token is implemented. I assume whitelisting specific domains is no option?
-
Consider the bearer token to be nice and all. So why would I even want to whitelist, if I have a working protection mechanism for the API?
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.