Discussion:
wrapping up for 2.1 and 2.2
Reinier Balt
2012-07-18 10:40:33 UTC
Permalink
Hi all,

I've fixed all reports on 2.1 and 2.2 that I can reproduce. I'd like to
publish 2.1.1 (rails2.3/ruby 1.8.7) and go towards 2.2 (rails3.2/ruby 1.8.7
& 1.9.3).

Are any of you willing/able to help with reproducing the remaining tickets?
Especially the tickets about marking deferred todos complete for both 2.1
and 2.2

And how do you feel about tracks 2.2 not supporting openid / ldap / cas,
i.e. only userid/password. Is this essential to support? An option could be
to integrate Device/OmniAuth in 2.2 but this is not trivial (migrating
current users to new framework). What do you think?

Reinier
Hans de Graaff
2012-07-23 18:07:22 UTC
Permalink
Post by Reinier Balt
And how do you feel about tracks 2.2 not supporting openid / ldap / cas,
i.e. only userid/password. Is this essential to support? An option could be
to integrate Device/OmniAuth in 2.2 but this is not trivial (migrating
current users to new framework). What do you think?
One approach here could be to trust the web server to provide the right
identity. One could then set up e.g. Apache to handle LDAP
authentication. Drawback is that you won't get a nice login page but the
browser popup instead. It looks like there are similar modules for CAS
and OpenID, but I have not used those.

At work we use authlogic which has some plugins for other authentication
methods, but in reality I find that each authentication framework needs
its own kind of hand-holding.

Kind regards,

Hans

Loading...