SUNScholar/Researcher Authorisation/Step 2 - Revision history

Ivdl: /* Step 2.2 - Configure LDAP */

2018-11-21T11:55:47Z

Step 2.2 - Configure LDAP

2018-11-20T05:46:11Z

Step 2.2 - Configure LDAP

2016-05-28T09:51:06Z

Step 2.2 - Configure LDAP

2016-05-28T09:33:27Z

Step 2.2 - Configure LDAP

2015-06-18T14:45:37Z

Step 2.1 - Enable LDAP

2015-06-07T20:17:57Z

PLEASE NOTE:

2015-06-07T20:17:27Z

PLEASE NOTE:

2015-06-07T20:17:04Z

PLEASE NOTE:

2015-06-07T20:16:47Z

PLEASE NOTE:

2015-06-06T21:12:18Z

@@ Line 26: / Line 26: @@
 Now modify the ldap config file as follows.
   nano $HOME/{{Source}}/dspace/config/modules/authentication-ldap.cfg
- authentication-ldap.provider_url = ...
+{{
+Quote | DSpace 6 changes | The example below applies to DSpace 5. For DSpace 6: All configuration options require an authentication-ldap prefix (e.g. authentication-ldap.provider_url), and all commas in the contexts need to be escaped with a backslash.
-This needs to be changed for every option individually. If you're using an older configuration file without adding the prefix, you will see NullPointerException errors upon login.
+}}
 <pre>

@@ Line 26: / Line 26: @@
 Now modify the ldap config file as follows.
   nano $HOME/{{Source}}/dspace/config/modules/authentication-ldap.cfg
-See example config below.
+The example below is suitable for DSpace 5 as is. '''Note that from DSpace 6 onwards, all the configuration options require an 'authentication-ldap.' prefix, e.g.'''
 <pre>
 #---------------------------------------------------------------#

@@ Line 204: / Line 204: @@
 '''Please note:''' The above configuration uses the insecure LDAP port '''389''', you may want to test using the insecure port of '''389''' and then move to the secure port of '''636'''.
 ----
-[[Category:Customisation]]
+[[Category:System Administration]]

← Older revision		Revision as of 09:33, 28 May 2016
Line 204:		Line 204:
	'''Please note:''' The above configuration uses the insecure LDAP port '''389''', you may want to test using the insecure port of '''389''' and then move to the secure port of '''636'''.		'''Please note:''' The above configuration uses the insecure LDAP port '''389''', you may want to test using the insecure port of '''389''' and then move to the secure port of '''636'''.
	----		----
		+	[[Category:Customisation]]

@@ Line 14: / Line 14: @@
 Edit the following file:
-  nano $HOME/{{Source}}]/dspace/config/modules/authentication.cfg
+  nano $HOME/{{Source}}/dspace/config/modules/authentication.cfg
 Add LDAP authentication, see example below.
@@ Line 22: / Line 22: @@
 	org.dspace.authenticate.PasswordAuthentication
 </pre>
 ===Step 2.2 - Configure LDAP===
 Now modify the ldap config file as follows.

@@ Line 4: / Line 4: @@
 ==<font color="red">'''''PLEASE NOTE''''':</font>==
-''During the upgrade from DSpace 1.8.2 to 3.2, the ldap config changed and it seems a bug was introduced: https://jira.duraspace.org/browse/DS-1781.
+During the upgrade from DSpace 1.8.2 to 3.2, the ldap config changed and it seems a bug was introduced: https://jira.duraspace.org/browse/DS-1781.
 Take special note of the "'''netid_email_domain = @example.com'''" parameter at the bottom of the file.
-If you do not specify an ''@example.com'' email suffix, then you will get '''null''' suffix errors for eperson email addresses.''
+If you do not specify an ''@example.com'' email suffix, then you will get '''null''' suffix errors for eperson email addresses.
 ==Step 2 - DSpace configuration==

@@ Line 1: / Line 1: @@
 <center>
-  '''[[SUNScholar/Researcher Authorisation| BACK TO RESEARCHER AUTHORISATION]]'''
+  '''[[SUNScholar/Researcher Authorisation/Step_3|NEXT - STEP 3]]'''
 </center>