From pedz at easesoftware.com Tue Oct 16 18:17:03 2007 From: pedz at easesoftware.com (Perry Smith) Date: Tue, 16 Oct 2007 17:17:03 -0500 Subject: [Ruby-activeldap-discuss] Reloadable no longer present Message-ID: <1BDA1388-4B72-4CA9-9DA5-736CD5F7D497@easesoftware.com> I just updated to the latest Rails -- this might be a mistake. Reloadable is no longer in fact, vendor/rails/activesupport/lib/ active_support/reloadable.rb is not longer present at all. Any suggestions of what to do? Thanks, Perry Smith ( pedz at easesoftware.com ) Ease Software, Inc. ( http://www.easesoftware.com ) Low cost SATA Disk Systems for IBMs p5, pSeries, and RS/6000 AIX systems -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/ruby-activeldap-discuss/attachments/20071016/0e649389/attachment.html From kou at cozmixng.org Tue Oct 16 20:45:07 2007 From: kou at cozmixng.org (Kouhei Sutou) Date: Wed, 17 Oct 2007 09:45:07 +0900 Subject: [Ruby-activeldap-discuss] Reloadable no longer present In-Reply-To: <1BDA1388-4B72-4CA9-9DA5-736CD5F7D497@easesoftware.com> References: <1BDA1388-4B72-4CA9-9DA5-736CD5F7D497@easesoftware.com> Message-ID: Hi, > I just updated to the latest Rails -- this might be a mistake. > > Reloadable is no longer in fact, > vendor/rails/activesupport/lib/active_support/reloadable.rb > is not longer present at all. > > Any suggestions of what to do? We can just ignore that. I've committed the code for that into trunk. Thanks, -- kou From gcowsar at gmail.com Thu Oct 25 10:33:07 2007 From: gcowsar at gmail.com (George Cowsar) Date: Thu, 25 Oct 2007 09:33:07 -0500 Subject: [Ruby-activeldap-discuss] ACL "foreign key" Message-ID: I found the source code online at ruby-activeldap.googlecode.com 1) I am used to installing with gem install, but how do you install from this source? 2) Why doesn't this work? Well I figured out part of it, but it leaves some questions ... script/console u = User.find('gcowsar') group_cn = u.primary_group.cn I get: NoMethodError: You have a nil object when you didn't expect it! I get a valid user u. And u.primary_group is: ActiveLdap::Association::BelongsTo:0x2aaab0e11880 @target=nil, @owner=#, @new_entry=false, @base=nil, @data={"gidNumber"=>["123"], "cn"=>["George Cowsar"], "givenName"=>["George"], ... But it isn't a Group object like I expected. AH HAH! I just figured it out. I need to have access to the group, and I don't because of ACLs. So I logged in again as the rootdn and it worked! Here are the 2 new questions: Is there a way for an ACL to allow access to a users "own" groups? But not other Groups? It seems like the original problem should have thrown a more meaningful exception, like "Unable to access cn=gcowsar,ou=Group..."? thanks, George From kou at cozmixng.org Fri Oct 26 07:41:33 2007 From: kou at cozmixng.org (Kouhei Sutou) Date: Fri, 26 Oct 2007 20:41:33 +0900 (JST) Subject: [Ruby-activeldap-discuss] ACL "foreign key" In-Reply-To: References: Message-ID: <20071026.204133.-586542096.kou@cozmixng.org> Hi, > 1) I am used to installing with gem install, but how do you install > from this source? If you are using with Rails, the following page will help you: http://code.google.com/p/ruby-activeldap/wiki/UsingTrunkWithRails > Here are the 2 new questions: > > Is there a way for an ACL to allow access to a users "own" groups? But > not other Groups? Each entry can have its own connection. Use ActiveLdap::Base#bind for this. And the following example code uses this feature: http://ruby-activeldap.googlecode.com/svn/trunk/examples/al-admin/app/models/ldap_user.rb > It seems like the original problem should have thrown a more > meaningful exception, like "Unable to access cn=gcowsar,ou=Group..."? We can't because LDAP server doesn't return such information. I think it's for security problem. Thanks, -- kou From gcowsar at gmail.com Fri Oct 26 10:43:10 2007 From: gcowsar at gmail.com (George Cowsar) Date: Fri, 26 Oct 2007 09:43:10 -0500 Subject: [Ruby-activeldap-discuss] ACL "foreign key" In-Reply-To: <20071026.204133.-586542096.kou@cozmixng.org> References: <20071026.204133.-586542096.kou@cozmixng.org> Message-ID: Thanks for the answers. One more point regarding: > We can't because LDAP server doesn't return such > information. I think it's for security problem. > I was careless when I provided my example exception which was: a more meaningful exception, like "Unable to access cn=gcowsar,ou=Group..." ... I understand that much "meaning" isn't possible because of access control, but if somehow more information could be provided in the primary_group object, maybe primary_group.last_exception could return "Unable to access requested entry". -George On 10/26/07, Kouhei Sutou wrote: > Hi, > > > 1) I am used to installing with gem install, but how do you install > > from this source? > > If you are using with Rails, the following page will help > you: > > http://code.google.com/p/ruby-activeldap/wiki/UsingTrunkWithRails > > > Here are the 2 new questions: > > > > Is there a way for an ACL to allow access to a users "own" groups? But > > not other Groups? > > Each entry can have its own connection. Use > ActiveLdap::Base#bind for this. And the following example > code uses this feature: > http://ruby-activeldap.googlecode.com/svn/trunk/examples/al-admin/app/models/ldap_user.rb > > > It seems like the original problem should have thrown a more > > meaningful exception, like "Unable to access cn=gcowsar,ou=Group..."? > > We can't because LDAP server doesn't return such > information. I think it's for security problem. > > > Thanks, > -- > kou > _______________________________________________ > Ruby-activeldap-discuss mailing list > Ruby-activeldap-discuss at rubyforge.org > http://rubyforge.org/mailman/listinfo/ruby-activeldap-discuss > From kou at cozmixng.org Sat Oct 27 00:19:48 2007 From: kou at cozmixng.org (Kouhei Sutou) Date: Sat, 27 Oct 2007 13:19:48 +0900 (JST) Subject: [Ruby-activeldap-discuss] ACL "foreign key" In-Reply-To: References: <20071026.204133.-586542096.kou@cozmixng.org> Message-ID: <20071027.131948.133610148.kou@cozmixng.org> Hi, > I was careless when I provided my example exception which was: > a more meaningful exception, like "Unable to access cn=gcowsar,ou=Group..." > > ... I understand that much "meaning" isn't possible because of access > control, but if somehow more information could be provided in the > primary_group object, maybe primary_group.last_exception could return > "Unable to access requested entry". Uhmm... I think "primary_group.nil? == true" means "Unable to access requested entry". Is it not enough? Thanks, -- kou From kou at cozmixng.org Sat Oct 27 01:24:40 2007 From: kou at cozmixng.org (Kouhei Sutou) Date: Sat, 27 Oct 2007 14:24:40 +0900 (JST) Subject: [Ruby-activeldap-discuss] ACL "foreign key" In-Reply-To: References: <20071027.131948.133610148.kou@cozmixng.org> Message-ID: <20071027.142440.109398768.kou@cozmixng.org> Hi, > But u.primary_group.nil? is actually false, u.primary_group is a > ActiveLdap::Association::BelongsTo and u.primary_group.cn throws an > exception: > You have a nil object when you didn't expect it! > > It would be better if u.primary_group.cn returned nil, and I get your > point that you can infer that it is because of access control. Ah, sorry. What about u.primary_group.target.nil?? Thanks, -- kou From kou at cozmixng.org Sat Oct 27 09:02:54 2007 From: kou at cozmixng.org (Kouhei Sutou) Date: Sat, 27 Oct 2007 22:02:54 +0900 (JST) Subject: [Ruby-activeldap-discuss] 0.8.4? Message-ID: <20071027.220254.04815732.kou@cozmixng.org> Hi, I added validation support by LDAP schema and acts_as_tree support. And I also updated a sample Rails application: http://pub.cozmixng.org/al-admin/ # I'm not good in design but I think it's design is more # better than ever before. ;p I think it's a good time for releasing 0.8.4. Will, what about do you think about this? 0.8.3 -> 0.8.4: * Improved DN handling. * Supported attribute value validation by LDAP schema. * Changed RubyGems name: ruby-activeldap -> activeldap. * Removed Log4r dependency. * Supported lazy connection establishing. * [API CHANGE]: establish_connection doesn't connect LDAP server. * [API CHANGE]: Removed ActiveLdap::Base#establish_connection. * Added ActiveLdap::Base#bind. (use this instead of #establish_connection) * Supported implicit acts_as_tree. * [API CHANGE]: Supported type casting. * Supported :uri option in configuration. * Improved Rails integration: * Followed Rails 2.0 changes. * AL-Admin: * Supported lang parameter in URL. * Improved design a bit. (Please someone help us!) * Rails plugin: * Added ActiveLdap::VERSION check. * Added model_active_ldap generator. * Renamed scaffold_al generator to scaffold_active_ldap. Thanks, -- kou From lists at suares.an Sat Oct 27 20:07:41 2007 From: lists at suares.an (Ace Suares) Date: Sat, 27 Oct 2007 20:07:41 -0400 Subject: [Ruby-activeldap-discuss] 0.8.4? In-Reply-To: <20071027.220254.04815732.kou@cozmixng.org> References: <20071027.220254.04815732.kou@cozmixng.org> Message-ID: <200710272007.41321.lists@suares.an> On Saturday 27 October 2007, Kouhei Sutou wrote: > Hi, > > I added validation support by LDAP schema and acts_as_tree > support. And I also updated a sample Rails application: > http://pub.cozmixng.org/al-admin/ > > # I'm not good in design but I think it's design is more > # better than ever before. ;p Yes Kou, it looks nicer... then before :-) It also works nicer with the + and - and such! cheers ace > > I think it's a good time for releasing 0.8.4. > Will, what about do you think about this? > > > 0.8.3 -> 0.8.4: > * Improved DN handling. > * Supported attribute value validation by LDAP schema. > * Changed RubyGems name: ruby-activeldap -> activeldap. > * Removed Log4r dependency. > * Supported lazy connection establishing. > * [API CHANGE]: establish_connection doesn't connect LDAP server. > * [API CHANGE]: Removed ActiveLdap::Base#establish_connection. > * Added ActiveLdap::Base#bind. (use this instead of > #establish_connection) * Supported implicit acts_as_tree. > * [API CHANGE]: Supported type casting. > * Supported :uri option in configuration. > * Improved Rails integration: > * Followed Rails 2.0 changes. > * AL-Admin: > * Supported lang parameter in URL. > * Improved design a bit. (Please someone help us!) > * Rails plugin: > * Added ActiveLdap::VERSION check. > * Added model_active_ldap generator. > * Renamed scaffold_al generator to scaffold_active_ldap. > > > Thanks, > -- > kou > _______________________________________________ > Ruby-activeldap-discuss mailing list > Ruby-activeldap-discuss at rubyforge.org > http://rubyforge.org/mailman/listinfo/ruby-activeldap-discuss From kou at cozmixng.org Tue Oct 30 07:38:01 2007 From: kou at cozmixng.org (Kouhei Sutou) Date: Tue, 30 Oct 2007 20:38:01 +0900 (JST) Subject: [Ruby-activeldap-discuss] 0.8.4? In-Reply-To: References: <20071027.220254.04815732.kou@cozmixng.org> Message-ID: <20071030.203801.-681999992.kou@cozmixng.org> Hi, In "Re: 0.8.4?" on Mon, 29 Oct 2007 09:52:15 -0700, "Will_Drewry?" wrote: > > I added validation support by LDAP schema and acts_as_tree > > support. And I also updated a sample Rails application: > > http://pub.cozmixng.org/al-admin/ > > > > I think it's a good time for releasing 0.8.4. > > Will, what about do you think about this? > > Sounds good to me! The changelog looks awesome! > Given the API changes, I'd think we should bump this to 0.9.0. In the > past I always determine version bumps using the following logic: > version = major_api_change.minor_api_change.no_api_change > > Does that sound reasonable, or do you think the changes are still > minor enough to fall under a new 0.8.x release? (E.g. can existing > applications use this release without changing their code?) OK. To follow the rule, we should use 0.9.0 for the next version. Thanks, -- kou