On Aug 13, 2011, at 6:00 AM, [email protected] wrote: > Send ECM mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.nuxeo.com/mailman/listinfo/ecm > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of ECM digest..." > Today's Topics: > > 1. Re: Local Configuration Directory Service (Florent Guillaume) > 2. Re: Local Configuration Directory Service (Sean Radford) > 3. Re: SSO CAS with Nuxeo 5.4.1 ([email protected]) > > From: Florent Guillaume <[email protected]> > Subject: Re: [Ecm] Local Configuration Directory Service > Date: August 12, 2011 7:59:34 AM EDT > To: Sean Radford <[email protected]> > Cc: [email protected] > > > It was chosen because it doesn't imply any changes in the user table format. > > > On Thu, Aug 11, 2011 at 3:37 PM, Sean Radford <[email protected]> wrote: >> I did think that you could use a Multi-Directory, but: >> >> 1. That doesn't seem very scalable to me. >> 2. There is the problem of getting the database to ensure uniqueness across >> the different tables. >> >> Does anyone know, the rationale for opting for this table-per-configuration >> approach? I do seem to recall Florent mentioning the use of the >> column-discriminator design in the past, so wondering why this alternative >> was chosen. >> >> Regards, >> >> Sean >> >> >> On 11/08/11 10:16, Thomas Roger wrote: >>> >>> Hi, >>> >>> To avoid having a context document for login, you should use a >>> MultiDirectory that wraps all the user directories, and do the >>> authentication against it. >>> Be aware that a user id should be unique across the different user >>> directories. >>> >>> -- >>> Thomas >>> >>> >>> >>> On 11 August 2011 09:18, Sean Radford<[email protected]> wrote: >>>> >>>> Hi, >>>> >>>> Been reading about the Local Configuration Directory Service >>>> >>>> (http://blogs.nuxeo.com/dev/2011/06/new-local-configuration-directory-service-first-step.html) >>>> and looking at the 5.4.3-SNAPSHOT source (in particular the >>>> UserManagerImpl >>>> that is the start of the multi tenant functionality). >>>> >>>> From my understanding, when a directory is opened, the actual underlying >>>> table that is used depends on the DirectoryLocalConfiguration of the >>>> Document in context. I can see how this works for vocabularies, but for >>>> users is there not an issue at login as there is never any Document in >>>> context and so you always query the same table for your user. >>>> >>>> Or am I missing something? >>>> >>>> Would it not be better to have an additional column in each directory >>>> table >>>> denoting the DirectoryLocalConfiguration value with all queries having >>>> the >>>> relevant value appended as an additional WHERE clause? You could then >>>> have a >>>> 'special case' context document to denote querying across all >>>> DirectoryLocalConfigurations for the login situation. >>>> >>>> Regards, >>>> >>>> Sean >>>> >>>> -- >>>> Dr. Sean Radford, MBBS, MSc >>>> http://www.tacola.com/ >>>> http://www.tacolaecm.com/ >>>> t: +44 (0)845 KEY HELP >>>> t: +44 (0)845 539 4357 >>>> m: +44 (0)7802 24 24 86 >>>> >>>> --- >>>> Mailing list: [email protected] >>>> Forum: http://forum.nuxeo.org/f/1/ >>>> >> >> >> -- >> Dr. Sean Radford, MBBS, MSc >> http://www.tacola.com/ >> http://www.tacolaecm.com/ >> t: +44 (0)845 KEY HELP >> t: +44 (0)845 539 4357 >> m: +44 (0)7802 24 24 86 >> >> --- >> Mailing list: [email protected] >> Forum: http://forum.nuxeo.org/f/1/ >> > > > > -- > Florent Guillaume, Director of R&D, Nuxeo > Open Source, Java EE based, Enterprise Content Management (ECM) > http://www.nuxeo.com http://www.nuxeo.org +33 1 40 33 79 87 > > > > > From: Sean Radford <[email protected]> > Subject: Re: [Ecm] Local Configuration Directory Service > Date: August 12, 2011 8:32:43 AM EDT > To: Florent Guillaume <[email protected]> > Cc: [email protected] > > > But upgrades often require table re-structuring (columns added and taken > away). > > As long as you are happy that this is a robust solution going forward, then > that's fine (though I'm not convinced). > > Regards, > > Sean > > > On 12/08/11 12:59, Florent Guillaume wrote: >> It was chosen because it doesn't imply any changes in the user table format. >> >> >> On Thu, Aug 11, 2011 at 3:37 PM, Sean Radford<[email protected]> >> wrote: >>> I did think that you could use a Multi-Directory, but: >>> >>> 1. That doesn't seem very scalable to me. >>> 2. There is the problem of getting the database to ensure uniqueness across >>> the different tables. >>> >>> Does anyone know, the rationale for opting for this table-per-configuration >>> approach? I do seem to recall Florent mentioning the use of the >>> column-discriminator design in the past, so wondering why this alternative >>> was chosen. >>> >>> Regards, >>> >>> Sean >>> >>> >>> On 11/08/11 10:16, Thomas Roger wrote: >>>> Hi, >>>> >>>> To avoid having a context document for login, you should use a >>>> MultiDirectory that wraps all the user directories, and do the >>>> authentication against it. >>>> Be aware that a user id should be unique across the different user >>>> directories. >>>> >>>> -- >>>> Thomas >>>> >>>> >>>> >>>> On 11 August 2011 09:18, Sean Radford<[email protected]> wrote: >>>>> Hi, >>>>> >>>>> Been reading about the Local Configuration Directory Service >>>>> >>>>> (http://blogs.nuxeo.com/dev/2011/06/new-local-configuration-directory-service-first-step.html) >>>>> and looking at the 5.4.3-SNAPSHOT source (in particular the >>>>> UserManagerImpl >>>>> that is the start of the multi tenant functionality). >>>>> >>>>> From my understanding, when a directory is opened, the actual underlying >>>>> table that is used depends on the DirectoryLocalConfiguration of the >>>>> Document in context. I can see how this works for vocabularies, but for >>>>> users is there not an issue at login as there is never any Document in >>>>> context and so you always query the same table for your user. >>>>> >>>>> Or am I missing something? >>>>> >>>>> Would it not be better to have an additional column in each directory >>>>> table >>>>> denoting the DirectoryLocalConfiguration value with all queries having >>>>> the >>>>> relevant value appended as an additional WHERE clause? You could then >>>>> have a >>>>> 'special case' context document to denote querying across all >>>>> DirectoryLocalConfigurations for the login situation. >>>>> >>>>> Regards, >>>>> >>>>> Sean >>>>> >>>>> -- >>>>> Dr. Sean Radford, MBBS, MSc >>>>> http://www.tacola.com/ >>>>> http://www.tacolaecm.com/ >>>>> t: +44 (0)845 KEY HELP >>>>> t: +44 (0)845 539 4357 >>>>> m: +44 (0)7802 24 24 86 >>>>> >>>>> --- >>>>> Mailing list: [email protected] >>>>> Forum: http://forum.nuxeo.org/f/1/ >>>>> >>> >>> -- >>> Dr. Sean Radford, MBBS, MSc >>> http://www.tacola.com/ >>> http://www.tacolaecm.com/ >>> t: +44 (0)845 KEY HELP >>> t: +44 (0)845 539 4357 >>> m: +44 (0)7802 24 24 86 >>> >>> --- >>> Mailing list: [email protected] >>> Forum: http://forum.nuxeo.org/f/1/ >>> >> >> > > > -- > Dr. Sean Radford, MBBS, MSc > http://www.tacola.com/ > http://www.tacolaecm.com/ > t: +44 (0)845 KEY HELP > t: +44 (0)845 539 4357 > m: +44 (0)7802 24 24 86 > > > > > > From: [email protected] > Subject: Re: [Ecm] SSO CAS with Nuxeo 5.4.1 > Date: August 12, 2011 11:44:07 AM EDT > To: [email protected] > > > Yes. The CAS2 extension (nuxeo-platform-login-cas2...) > appears to be initialising correctly when nuxeo starts up in > tomcat. However, when I hit the web service that we've > created, the CAS2_AUTH is not being called. Am I missing a > configuration file or filter mapping? > > > > _______________________________________________ > ECM mailing list > [email protected] > http://lists.nuxeo.com/mailman/listinfo/ecm
--- Mailing list: [email protected] Forum: http://forum.nuxeo.org/f/1/
