Problem solved.  My own fault.  I had re-deployed and somehow had the 
autoregister set to true in the LDAP config file.

Best regards,

Don.

On Tuesday, April 18, 2017 at 8:32:16 AM UTC-4, Donald Bynum wrote:

> I am running DSpace 5.5 with XMLUI and Oracle.  I am seeing very unwanted 
> behavior when a user logs in.  Here are the details of my config:
>
> I am using LDAP authentication - that's appears to be working, in as much 
> as all users can login using their LDAP credentials.  The issue I am seeing 
> is as follows:
>
> I have a user who already has an eperson record with say eperson_id=100 
> and that eperson has an email address of b...@thing.org in the eperson 
> database record..  That eperson is assigned to various authorizations 
> (COllection Admins, etc.).  Whne that person authenticates via the login 
> page, what happens is that a brand new eperson record is created with 
> eperson_id=101, with just the userid in the eperson email column in the 
> eperson table, i.e. bob.  That new eperson, of course, has no 
> authorizations, since they were just created as a function of logging in.
>
> I have deleted via the UI, the original eperson record (the one with 
> b...@thing.org) with eperson_id-100 and also the newly created one with 
> eperson_id=101.  So, now that user has no eperson records.  I then ask that 
> user to try and login and it is successful with yet another simple eperson 
> record created (again with just bob in the email address and 
> eperson_id=102).
>
> What am I missing or what is mis-configured such that this is happening?
>
> Any help would be very much appreciated.
>
> Regards,
>
> Don Bynum
>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Reply via email to