From: pmulder <mulder.patrick@gmail.com>
To: Rack Development <rack-devel@googlegroups.com>
Subject: Experiment with Rack authentication middleware
Date: Sun, 13 Jan 2013 09:36:54 -0800 (PST) [thread overview]
Message-ID: <45cbe83d-5aea-49ae-8098-a14131d3d41b@x10g2000yqx.googlegroups.com> (raw)
Hello,
I was looking into using Rack for authenticating users across multiple
Rack applications (that might live on different domains, e.g.
example.com and api.example.com or app1.herokuapp.com and
app2.herokuapp.com)
Now, I wrote a small Rack middleware to help with this:
https://github.com/mulderp/rack-api-auth
It's still very, very basic, but maybe someone here feels interested
to share thoughts on this; combine efforts or can give some pointers
to improve on the code.
Thanks in any case for your interest.
Patrick
reply other threads:[~2013-01-13 17:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://groups.google.com/group/rack-devel
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45cbe83d-5aea-49ae-8098-a14131d3d41b@x10g2000yqx.googlegroups.com \
--to=rack-devel@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).