<quote who="Carl Johnstone"> >> Externally in your organisation? > > No to an external organisation that has been contracted by us to provide and > host a web application. This application needs to share a single sign-on with applications built in-house using Catalyst.
Ah, ok. What Directory server are you using btw? > >> For configuration, why don't you have one set and reference it from both *::LDAP ?? >> >> Or I am being dumb here? > > No you're right that I can combine some of the configuration and reference it accordingly. However I don't have a single obvious place to add an extra > method (although J Rockway may have a hack around that). Sounds good. > >> You're pulling LDAP users into your RDBMS? Why not keep them there? If you >> are using PostgreSQL you can use dblink-ldap as a function. Might be handy. > > No I've got data in my RDBMS that has a relationship to the data in my LDAP > directory. For example "comments" are added by users, therefore the comments > in the database have a submitter for which the details are held in LDAP. > > dblink-ldap is interesting but we're a MySQL shop. I'm also taking a look at > DBD::LDAP on CPAN which does a similar thing in perl-land. Understood. > > Carl > > > _______________________________________________ > List: [email protected] > Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: > http://www.mail-archive.com/[email protected]/ > Dev site: http://dev.catalyst.perl.org/ > _______________________________________________ List: [email protected] Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[email protected]/ Dev site: http://dev.catalyst.perl.org/
