Thanks to everyone for your help on this issue and the issue with the url 
showing incorrectly in the BE.  The issue seems to been caused by the BE server 
not reading the local.cfg file but only the dspace.cfg file.  I am not sure 
what caused the issue, but once I recreated the local.cfg file from scratch 
things started to perform as expected.

From: DSpace Technical Support <dspace-tech@googlegroups.com>
Sent: Tuesday, August 22, 2023 11:53 AM
To: DSpace Technical Support <dspace-tech@googlegroups.com>
Subject: [dspace-tech] Re: LDAP authentication and Dspace 7.6

Hi Dale,

The DSpace backend's logging configs are in [dspace]/config/log4j2.xml.  So, 
you should be able to use that file to increase logging as needed.  By default 
though, the backend should log information about attempted LDAP logins, so I'm 
surprised you aren't seeing anything in your dspace.log file.

You also may want to look at the troubleshooting guide to help you check to see 
if there are *different* errors in the User Interface layer that are perhaps 
blocking LDAP's ability to function properly. See 
https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)

Tim
On Tuesday, August 22, 2023 at 10:32:56 AM UTC-5 
dale.p...@vanderbilt.edu<mailto:dale.p...@vanderbilt.edu> wrote:
Good morning,

We are still working to migrate from DSpace 6.x .  We have LDAP working in 
DSpace 6 but it does not work in 7.  We have copied over the credentials,  
enabled it in local.cfg and also in the authentication-ldap.cfg as a test – 
still no luck.  The main issue I am experiencing is that nothing is being 
logged.   Any suggestions on increasing logging?  We are running the FE in dev 
mode (yarn start:dev) .


-Dale

[Vanderbilt]<https://www.vanderbilt.edu/>

Dale Poulter
Director, Library Technology and Digital Services
Vanderbilt Libraries | Vanderbilt University
615-343-5388<tel:(615)%20343-5388> | dale.p...@vanderbilt.edu | 
https://www.library.vanderbilt.edu<https://www.library.vanderbilt.edu/>

Pronouns: he/him/his

My working day may not be your working day. Please do not feel obliged to reply 
to this email outside of your normal working hours.


--
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
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<mailto:dspace-tech+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/f23973bc-9a9a-45c4-a491-804d14e2f840n%40googlegroups.com<https://groups.google.com/d/msgid/dspace-tech/f23973bc-9a9a-45c4-a491-804d14e2f840n%40googlegroups.com?utm_medium=email&utm_source=footer>.

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/BN0PR08MB74708B689EFD942103B456F0FEF3A%40BN0PR08MB7470.namprd08.prod.outlook.com.

Reply via email to