EPrints Technical Mailing List Archive
Message: #06260
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
Re: [EP-tech] LDAP login
- To: "eprints-tech@ecs.soton.ac.uk" <eprints-tech@ecs.soton.ac.uk>
- Subject: Re: [EP-tech] LDAP login
- From: Andrew Beeken <anbeeken@lincoln.ac.uk>
- Date: Thu, 9 Feb 2017 15:58:40 +0000
The use case for us is the generation of pages for creators. As a background, we currently do LDAP login via a bulk import, but the script that controls this is quite destructive and is intrinsically tied into a number of core EPrints files
which I want to get away from – basically it tears down the user table nightly, reimports a fresh dump from LDAP but also harvests off any users who may have left the university into a separate table. One of the things that using their internal staff number,
which is a six digit numeric string, does for us is it allows us to use a constant identifier for that member of staff across all systems we want to join up. Take, for example, a user John Smith with username jsmith and staff ID of 123456. John can log into the system using his normal user details through LDAP authentication which is fine, but when his creator browse page is created it is as
http://eprints.lincoln.ac.uk/view/creators/123456.html which is great for us to be able to point other systems or apps at to drag his records back and use on, say, our internal staff directory. For us it’s that single point of truth that we know we can use
everywhere as an identifier, as well as not making members of staff use a different login for different systems. From: eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk]
On Behalf Of Lizz Jennings What’s the use case for the id being the internal one, rather than an EPrints one? We’ve got the internal id as the username, which seems to be effective. Lizz -- Lizz Jennings BA MSc ACLIP MCLIP (Revalidated 2015) Research Data Librarian (Systems) The Library 4.10, University of Bath, Bath, BA2 7AY UK Ext. 3570 (External 01225 383570) Research Data Management:
http://www.bath.ac.uk/research/data From:
eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk]
On Behalf Of Andrew Beeken Okay, related to but separate from my ongoing quest to migrate and improve our EPrints install, I’m looking into options for getting an LDAP authentication script up and running. I’ve had a look online and found a couple of different ways
to implement this, one of which (http://wiki.unimas.my/unimaswiki//bin/view/HOW-TO,+Tutorial+&+User+Manual/HOW-TO+:+Install+Eprints+v3.3.12++on+Ubuntu+14.04+With+LDAP+Authentication)
I’ve tried to no avail. Does anyone have any particular way of implementing this that they can recommend? I’m on the fence as to whether we should be doing this on a bulk import or creating users as and when they log in, however I DO want to ensure that the ID
associated with the user is the one from our internal system and not a naturally generated one from EPrints. As always, thanks in advance! Andrew
|
- References:
- [EP-tech] LDAP login
- From: Andrew Beeken <anbeeken@lincoln.ac.uk>
- Re: [EP-tech] LDAP login
- From: Lizz Jennings <E.Jennings@bath.ac.uk>
- [EP-tech] LDAP login
- Prev by Date: [EP-tech] trac.eprints.org
- Next by Date: Re: [EP-tech] LDAP login
- Previous by thread: Re: [EP-tech] LDAP login
- Next by thread: Re: [EP-tech] LDAP login
- Index(es):