Differences

This shows you the differences between two versions of the page.

--- en:user_advanced:user_management [2017/08/03 00:23] – kjdon
+++ en:user_advanced:user_management [2018/08/27 00:08] (current) – removed kjdon
@@ Line 1: / Line 1: @@
-====== User Management ======
-Greenstone software comes equipped with a system for registering and administering users. Greenstone users can register as a user with a login and password. Administrators can then assign them into various groups. These user groups are used for authenticating login to a [[en:user_advanced:remote_greenstone| remote Greenstone server]], and for [[en:user_advanced:security|password protecting collections and documents]].
-TODO:
-  * Registering as a user
-  * User groups
-  * Editing users
-===== GS3 Tomcat authentication notes =====
-We use Tomcat Realm to connect to JDBC database of users. Its specified in
-resources/tomcat/greenstone3.xml.in (which gets copied to resources/tomcat/context-name.xml, and then to packages/tomcat/conf/Catalina/localhost/context-name.xml
-<code>
-<!--
-   For embedded derby db:
-   driverName="org.apache.derby.jdbc.EmbeddedDriver"
-   connectionURL="jdbc:derby:@gsdl3webhome@/etc/usersDB"
--->
-<Realm className="org.apache.catalina.realm.JDBCRealm"
-        driverName="org.apache.derby.jdbc.ClientDriver"
-        connectionURL="jdbc:derby://@derbyserver@:@derbyserverport@/@gsdl3webhome@/etc/usersDB"
-        userTable="users" userNameCol="username" userCredCol="password"
-        userRoleTable="roles" roleNameCol="role"
-        />
-</code>
-Will end up like
-<code>
-<Realm className="org.apache.catalina.realm.JDBCRealm"
-        driverName="org.apache.derby.jdbc.ClientDriver"
-        connectionURL="jdbc:derby://localhost:1527//greenstone/greenstone3/web/etc/usersDB"
-        userTable="users" userNameCol="username" userCredCol="password"
-        userRoleTable="roles" roleNameCol="role"
-                />
-</code>
-Logins timeout when the tomcat session expires. Session expiry happens after a specified period of inactivity. In LibraryServlet.java, have
-<code>
-/**
-  * the maximum interval that the cached info remains in session_ids_table
-  * (in seconds) This is set in web.xml
-  */
-  protected int session_expiration = 1800;
-</code>
-This can be overridden by putting a session-expiration init-param into your servlet specification in web/WEB-INF/servlets.xml (which is included by web.xml). This is specified in seconds.
-<code>
-<init-param>
-  <param-name>session_expiration</param-name>
-  <param-value>3600</param-value>
-</init-param>
-</code>