[Xerte-dev] Re: upgrading and ldap

[Julian Tenney]

I meant for upgrade situations where the existing install is working, and folk (i.e. me) want it to be easy to upgrade...

-----Original Message-----
From: xerte-dev-bounces at lists.nottingham.ac.uk [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Pat Lockley
Sent: 30 August 2012 10:24
To: For Xerte technical developers
Subject: [Xerte-dev] Re: upgrading and ldap

the installer never used to put details into the ldap table, only ever went into the sitedetails table.

Guessing the new auth code only uses the ldap table, and so the installer needs to either do both, or just one, depending on what the preference is

On Thu, Aug 30, 2012 at 10:15 AM, Julian Tenney <Julian.Tenney at nottingham.ac.uk> wrote:
> How hard would it be to automate step 4?
>
>
>
> From: xerte-dev-bounces at lists.nottingham.ac.uk
> [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Ron 
> Mitchell
> Sent: 10 August 2012 09:40
> To: 'For Xerte technical developers'
> Subject: [Xerte-dev] Re: upgrading and ldap
>
>
>
> A quick update..
>
> This was the process that worked for upgrading an existing 1.7 install 
> using LDAP for authentication to 1.8
>
>
>
> 1. backup existing database and directory just in case
>
> 2. drop 1.8 code over top of existing code (for an upgrade you don't 
> need the setup folder)
>
> 3. visit the install to test the basics are working ok via guest access e.g.
> create and test an LO
>
> 4. manually add the existing ldap details currently in the sitedetails 
> table to the ldap table in the database
>
> 5. change from guest to ldap in config.php by commenting/un-commenting 
> the relevant line
>
> 6. refresh index.php and test login via ldap
>
>
>
> As I mentioned previously not sure if there's supposed to be an 
> automated way of transferring ldap details from the sitedetails table 
> to the ldap table?
>
>
>
> The other thing I'm not sure about is that the ldap table contains 
> ldap_knownname as a field that can't be empty and is created by 
> basic.sql in a new install and also exists in a 1.7 install yet I 
> can't find anywhere ldap_knownname is used in either 1.7 or 1.8 code. 
> Should this be removed from basic.sql?
>
>
>
> HTH
>
> Ron
>
>
>
> From: xerte-dev-bounces at lists.nottingham.ac.uk
> [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Julian 
> Tenney
> Sent: 09 August 2012 10:39
> To: For Xerte technical developers
> Subject: [Xerte-dev] Re: upgrading and ldap
>
>
>
>> I guess these are questions for David or Pat
>
> Yep. But we need to make this easy, otherwise people are going to get 
> in a mess / screw up their installs.
>
>
>
> From: xerte-dev-bounces at lists.nottingham.ac.uk
> [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Ron 
> Mitchell
> Sent: 09 August 2012 10:31
> To: 'For Xerte technical developers'
> Subject: [Xerte-dev] Re: upgrading and ldap
>
>
>
> Hi Julian
>
> yes I can see it cropping up regularly once people start trying to 
> upgrade as opposed to a new install. But at the moment I don't have 
> the answers to my two questions and especially question 1.
>
>
>
> Not sure if perhaps 1.8 code should look in sitedetails as well as the 
> ldap table for existing installs or if upgrade.php isn't working as it should.
> Not even sure if upgrade.php is meant to achieve this transfer of ldap 
> info from sitedetails to ldap? On a new install the values added 
> during install or via management.php go into the ldap table but not 
> sure what's supposed to happen for existing installs?
>
>
>
> In 1.8 /library/xerte/authentication/ldap code the note says:
>
>
>
> * For this to work, you'll need to have at least one entry in the XOT 'ldap'
> table.
>
>
>
> What is supposed to happen for existing installs where the ldap values 
> are in sitedetails and also some field/column names differ?
>
>
>
> I guess these are questions for David or Pat or perhaps Thomas has 
> encountered/resolved this too?
>
>
>
> HTH
>
> Ron
>
>
>
> From: xerte-dev-bounces at lists.nottingham.ac.uk
> [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Julian 
> Tenney
> Sent: 09 August 2012 09:56
> To: For Xerte technical developers
> Subject: [Xerte-dev] Re: upgrading and ldap
>
>
>
> Ron, would you mind documenting this process thoroughly, as you find 
> out how to do it, because this is going to come up a lot. If we get 
> one good, thorough set of instructions it will save us a load of pain. 
> Maybe there is an upgrade script or something we could write?
>
>
>
> Thanks,
>
>
>
> Julian
>
>
>
> From: xerte-dev-bounces at lists.nottingham.ac.uk
> [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Ron 
> Mitchell
> Sent: 08 August 2012 18:29
> To: 'For Xerte technical developers'
> Subject: [Xerte-dev] upgrading and ldap
>
>
>
> Hi all
>
> I had a chance to test an upgrade to 1.8 of a previous 1.7 install 
> which uses ldap today. The previous and working install had the ldap 
> values in site details rather than the separate ldap table.
>
>
>
> Upgrade process:
>
> drop code over top
>
> this then defaults to guest access but useful for checking the basics 
> work
>
> change from guest to ldap in config.php by commenting/un-commenting 
> the relevant line
>
> refresh index.php and try to login via ldap
>
> get error message LDAP servers not configured in DB
>
> visit management.php and check - ldap details displayed but not saved 
> to ldap table in db - clearly coming from site-details
>
> try running upgrade.php indicates nothing to upgrade
>
>
>
> Questions:
>
> 1. what's the process for transferring the ldap details from 
> site_details to ldap table for an existing install?
>
> In this case I can enter direct in the db but that's surely not the 
> intended method?
>
>
>
> 2. In the ldap table what typically goes in ldap_knowname?
>
>
>
> Cheers
>
> Ron
>
>
>
> This message and any attachment are intended solely for the addressee 
> and may contain confidential information. If you have received this 
> message in error, please send it back to me, and immediately delete 
> it. Please do not use, copy or disclose the information contained in 
> this message or in any attachment. Any views or opinions expressed by 
> the author of this email do not necessarily reflect the views of the University of Nottingham.
>
> This message has been checked for viruses but the contents of an 
> attachment may still contain software viruses which could damage your computer system:
> you are advised to perform your own checks. Email communications with 
> the University of Nottingham may be monitored as permitted by UK legislation.
>
>
> _______________________________________________
> Xerte-dev mailing list
> Xerte-dev at lists.nottingham.ac.uk
> http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev
>
> This message and any attachment are intended solely for the addressee 
> and may contain confidential information. If you have received this message in
> error, please send it back to me, and immediately delete it.   Please do not
> use, copy or disclose the information contained in this message or in 
> any attachment.  Any views or opinions expressed by the author of this 
> email do not necessarily reflect the views of the University of Nottingham.
>
> This message has been checked for viruses but the contents of an 
> attachment may still contain software viruses which could damage your computer system:
> you are advised to perform your own checks. Email communications with 
> the University of Nottingham may be monitored as permitted by UK legislation.
>
>

_______________________________________________
Xerte-dev mailing list
Xerte-dev at lists.nottingham.ac.uk
http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev