Commit Graph

18 Commits

Author SHA1 Message Date
Saj Goonatilleke 33403daf59 Remove Ptr from identifier names
This is not customary in Go.
2019-05-15 17:13:43 +10:00
Saj Goonatilleke d776ff7bcd Optionally use DNS SRV records for origin discovery 2019-05-07 04:48:50 +10:00
Andrew Schleifer 8bea12489d option for whitelisted /path 2018-09-21 15:01:59 +08:00
Rafael dos Santos Silva 15ab750172 FIX: Discourse groups now are in CSV format instead of an array 2018-07-23 22:48:33 -03:00
Matt Palmer 017810a752 Allow HTTP timeouts to be configurable 2017-11-22 09:05:10 +11:00
Matt Palmer 21ea40b9ba More logging for basic auth support
Need to know where things go missing.
2017-11-10 12:24:42 +11:00
Matt Palmer 385c8aea44 Guard LRU cache against concurrent access
Our chosen LRU cache implementation is not, as it turns out, thread-safe.
So we need to cast mutexes around to make everything OK.
2017-10-31 17:18:59 +11:00
Rafael dos Santos Silva 22af9254a5 Feature: Group handling 2017-10-25 23:32:39 -02:00
Matt Palmer 2d8643d593 Don't panic if we don't find the nonce in the cache 2017-10-03 20:33:47 +11:00
Matt Palmer febc3e4fe3 Support HTTP basic auth, allow username header name to be overridden
The big change here is to support an extremely limited form of HTTP basic
auth, for those situations when you've got some subset of requests coming in
which still need to be authenticated, but which aren't able to authenticate
via Discourse SSO.  The intended use case is for webhooks and other
progammatic access methods.  It is not intended to be a fully-featured HTTP
auth method (it only supports a single hard-coded user/password pair), but
instead an extremely simplistic "escape hatch".

If you need more complicated HTTP authentication, you probably want to
install nginx and do some crazy proxy chain games.  Best of luck to you with
that.

To avoid getting in the way of the SSO flow, the HTTP authentication is done
"blind"; that is, a `WWW-Authenticate` is never sent in a response.  This
may get up the nose of some user agents, however I can't see an easy way
around this.

Allowing the username header to be changed to something other than
Discourse-User-Name is a smaller change, needed to support third-party
software which looks for the authenticated username in a different header,
and which can't be overridden without a hammer and chisel.
2017-09-28 11:09:18 +10:00
AJ Bowen b604480504
Invert admin restriction UX 2017-06-07 19:49:18 +02:00
AJ Bowen abe0105423
Only restrict auth-proxy access to admin users if -admin-only flag is provided 2017-06-07 18:48:56 +02:00
Guo Xiang Tan 524f0697de Replace package that is no longer available. 2016-07-14 15:07:55 +08:00
Kane York aeca145eda Update README with new usage, fix the build 2015-08-24 17:10:27 -07:00
Kane York 1535c15f98 Add support for separate listen & proxy URIs 2015-08-22 13:37:21 -07:00
Sam 37ac0a471a correct missing cookie behavior 2015-04-15 15:04:16 +10:00
Sam 31b15c200e work in progress dockerfile 2015-04-15 14:02:33 +10:00
Sam 729f57a166 Initial commit 2015-04-15 13:18:18 +10:00