[Xerte] Re: Additional account?

Fri Sep 27 15:43:14 BST 2013

err yes but point of clarity.

The static.php I attached goes in the root folder and is what you point
those users to.

The static.php you add the usernames to is entirely different and exists in
\library\Xerte\Authentication\Static.php

HTH

Ron

From: xerte-bounces at lists.nottingham.ac.uk
[mailto:xerte-bounces at lists.nottingham.ac.uk] On Behalf Of Julian Tenney
Sent: 27 September 2013 15:29
To: Xerte discussion list
Subject: [Xerte] Re: Additional account?

Yeah, in static.php:

    /** Edit this list to your hearts content ... */

    private $_users = array(

        'username_here' => array("username" => "username_here", "password"
=> "password_here", "firstname" => "FirstName", "surname" => "Surname"),

    );

From: xerte-bounces at lists.nottingham.ac.uk
[mailto:xerte-bounces at lists.nottingham.ac.uk] On Behalf Of Sheppard, Nick
Sent: 27 September 2013 15:17
To: Xerte discussion list
Subject: [Xerte] Re: Additional account?

Thanks Ron. I've had a go in lieu of getting sftp access for my colleague
who actually understands php so bear with me.

I've done as you said* and I now get a log-in page at /static.php which is
what I expect I should expect.but I'm not clear how to configure a
uname/pword (presumably in static.php?)

* My auth_config.php now looks like this:

if ($static == true){

$xerte_toolkits_site->authentication_method = 'Static';

}else{

//$xerte_toolkits_site->authentication_method = 'Guest';

$xerte_toolkits_site->authentication_method = 'Ldap';

//$xerte_toolkits_site->authentication_method = 'Db';

$xerte_toolkits_site->authentication_method = 'Static';               

//$xerte_toolkits_site->authentication_method = "Moodle";

Nick

From: xerte-bounces at lists.nottingham.ac.uk
[mailto:xerte-bounces at lists.nottingham.ac.uk] On Behalf Of Ron Mitchell
Sent: 27 September 2013 14:50
To: 'Xerte discussion list'
Subject: [Xerte] Re: Additional account?

Try the attached - hope it gets through. Rename both with .php rather than
.txt

Here's the principle.

create a new very basic php page which the static login people should go to
e.g. static.php

this would be unique to your install and therefore not broken by upgrades

set a session variable in there e.g. set static to true and then redirect to
index.php

edit auth_config.php and check for that session and switch to static
authentication if that session is set

So the only page you would have to protect from upgrades is auth_config.php
which to be honest if you're upgrading regularly you need to do anyway

HTH

Ron

From: xerte-bounces at lists.nottingham.ac.uk
[mailto:xerte-bounces at lists.nottingham.ac.uk] On Behalf Of Julian Tenney
Sent: 26 September 2013 09:46
To: Xerte discussion list
Subject: [Xerte] Re: Additional account?

Yes, you can. I forget the exact details.

Normal users continue to login through the normal page.

'special' users should log in at yourtoolkits/static.php

And you configure their uname / pword in static.php

I think that's it. I can't remember if I need to change something to handle
the 'try ldap if fail try static' logic. Give it a whirl.

From: xerte-bounces at lists.nottingham.ac.uk
[mailto:xerte-bounces at lists.nottingham.ac.uk] On Behalf Of Sheppard, Nick
Sent: 26 September 2013 09:35
To: xerte at lists.nottingham.ac.uk
Subject: [Xerte] Additional account?

Hello

Is there any way to set up an additional non-LDAP account in xot? I have a
dev install that is only synced with staff LDAP - there's no way they'll
implement for students at this stage but I've an enthusiastic academic with
an enthusiastic final year student who would like to use it.

Thanks

Nick

To view the terms under which this email is distributed, please go to
http://disclaimer.leedsmet.ac.uk/email.htm

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.

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.

To view the terms under which this email is distributed, please go to
http://disclaimer.leedsmet.ac.uk/email.htm

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.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nottingham.ac.uk/pipermail/xerte/attachments/20130927/a1299f85/attachment-0001.html>