Re:You can not simply publicly access private secure links, ...
by paulgb on Friday March 08, 2024 @05:32AM
(#39639772)
For better or worse, basic auth in the URL isn't really an option any more, (e.g. see https://stackoverflow.com/a/57193064). I think the issue was that it reveals the secret to anyone who can see the URL bar, but the alternative we got still has that problem and also has the problem that the secret is no longer separable from the resource identifier.
Re:You can not simply publicly access private secure links, ...
by thayne on Friday March 08, 2024 @02:54PM
(#39645542)
The browser could hide the secret after it is entered.
Re:You can not simply publicly access private secure links, ...
by paulgb on Friday March 08, 2024 @10:01PM
(#39649071)
Yeah, and it would still be useful for queries that never appear in the URL bar (like EventSource and WebSocket, where setting an Authorization header is not something that’s exposed by the browser)
Technically you're right -- after all sending an authentication as a separate header doesn't make any difference.
or Sends the same data over the wire.However software treats URLs differently to headers. They sit in browser histories, server logs, get parsed by MITM firewalls, mined by browser extensions, etc
using https://user:[email protected]/endpoint or https://auth:[email protected]/endpoint
Would be better than
https://site.com/endpoint/user/pass or https://site.com/endpoint/?auth=token
As the former is less likely to be stored, either on the client or on the server. I don't do front end (or backend authentication -- I just rely on x509 client certs or oidc and the web server passes the validated username)