Express Auth now up and running in connect (Express-auth is dead, long live connect-auth)

[Ciaran]

Hi All,

I meant to post this last night, but the first preview release (0.0.1
;) ) of connect-auth ( http://github.com/ciaranj/connect-auth ) is up
and running. It is available from npm or github and should function
as a nearly drop in replacement for any existing express-auth (you
won't need to change any of your route code, just maybe change some
requires)

This means out of the box when using express with connect you can
setup single sign on against :

* HTTP Basic + Digest
* Yahoo
* Facebook
* Github
* Twitter
* Any custom strategy you care to design + implement

Far from complete, the tests + original (express) example don't
currently work, but I've tested (manually, ughhh) each of the other
strategies to ensure they work.

N.B. This module has a dependency on node-oauth
(http://github.com/ciaranj/node-oauth) which is also available as an
npm module ('oauth')

Feedback as always wanted, the API is not finished and I intend to
re-factor out a lot of the crud that is there purely due to the plugin
arch. of express that is no longer needed :) Should be perfectly
usable though <g>

-cj.

[Validatorian]

Fantastic! Excellent work Ciaran

On Jul 19, 5:19 am, Ciaran <ciar...@gmail.com> wrote:
> Hi All,
>
> I meant to post this last night, but the first preview release (0.0.1

> ;) ) of connect-auth (http://github.com/ciaranj/connect-auth) is up

[Michael Fellinger]

I've got some code for authentication with Janrain, could that be integrated?
See http://gist.github.com/481592 for the .js and .coffee

> --
> You received this message because you are subscribed to the Google Groups "Express" group.
> To post to this group, send email to expre...@googlegroups.com.
> To unsubscribe from this group, send email to express-js+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/express-js?hl=en.
>
>

--
Michael Fellinger
CTO, The Rubyists, LLC

[vision media [ Tj Holowaychuk ]]

I think there is a connect janrain middleware, if you check our wiki. I have not

personally used it though

Tj Holowaychuk
Vision Media
President & Creative Lead

[Ciaran]

On Mon, Jul 19, 2010 at 5:03 PM, Michael Fellinger
<m.fel...@gmail.com> wrote:
> I've got some code for authentication with Janrain, could that be integrated?
> See http://gist.github.com/481592 for the .js and .coffee

I see no reason why not, but I don't know enough about janrain to
comment ? Does it support a notion of delegated single sign on?
-cj.

[Michael Fellinger]

On Tue, Jul 20, 2010 at 1:11 AM, vision media [ Tj Holowaychuk ]
<t...@vision-media.ca> wrote:
> I think there is a connect janrain middleware, if you check our wiki. I have
> not
> personally used it though

Oh, wasn't aware of that, thanks :)

[Ciaran]

Yeah, I'll fold in a janrain SSO strategy as an example for
connect-auth, looks trivial
-cj.

[vision media [ Tj Holowaychuk ]]

looks a little sketchy but this is the one I was talking about http://github.com/xrd/connect-rpx

[Ciaran]

yeah I see it, have avoided looking at it so I can clean-room the
strategy as an exercise ;)
-cj.

On Mon, Jul 19, 2010 at 5:41 PM, vision media [ Tj Holowaychuk ]

[Ciaran]

I did this as an experiment,
http://github.com/ciaranj/connect-auth/blob/master/lib/auth.strategies/janrain.js
This strategy supports both the embedded style of janrain SSO (iframe
or link) or will automatically redirect to a sign-in page when trying
to access authenticated routes (will redirect back to the original
route attempt on completion when using the latter approach)

Could do with some fleshing out and fixing, but I'd like to
concentrate on getting my tests re-written to work against connect (I
know I suck!)

Please be aware that due to an issue in the current NPM connect
package, this particular strategy only works with the current HEAD
version of connect (read, *NOT* the npm package for connect)
-cj.