Metacat: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362003-04-18T18:36:08ZEcoinformatics Redmine
Redmine Bug #1048 (Resolved): create delete from ldap table codehttps://projects.ecoinformatics.org/ecoinfo/issues/10482003-04-18T18:36:08ZDavid Blankmandblankman@lternet.edu
<p>Once the insert or update is successful, delete the record ffrom the ldap table.</p>
<p>need to capture the $emailalias value.</p>
<p>delete from LDAP where emailalias = $emailalias</p> Bug #1047 (Resolved): Create triggers on LTER tables for ldap inserthttps://projects.ecoinformatics.org/ecoinfo/issues/10472003-04-18T18:32:17ZDavid Blankmandblankman@lternet.edu
<p>Need insert and update triggers for person, contact, lter tables. to insert<br />records into LDAP table.</p> Bug #1046 (Resolved): LTER LDAP database coordination perl script changeshttps://projects.ecoinformatics.org/ecoinfo/issues/10462003-04-18T18:24:38ZDavid Blankmandblankman@lternet.edu
<p>need success and failure messages & rountines built into perl scripts since ldap<br />inserts will be done behind the scenes.</p>
<p>success log file: uid, date<br />failure email to ? information needed: uid, action status, error message</p> Bug #1032 (Resolved): Metacat replication needs email for failure (hub especially)https://projects.ecoinformatics.org/ecoinfo/issues/10322003-04-08T23:51:13ZDavid Blankmandblankman@lternet.edu
<p>During current hub replication tests the replication stopped after 980 of approx<br />2700 documents. In addition to improving the error handling, an email should be<br />sent to all hub metacat administrators if a failure happens. While this is most<br />critical at initial startup when large numbers of documents may be replicated.<br />The bulk upload from lter sites may also create significant traffic. The email<br />message should include at least docid.</p> Bug #641 (Resolved): readme for metacat 1.2 needs modification (datafilepath)https://projects.ecoinformatics.org/ecoinfo/issues/6412002-10-18T19:05:06ZDavid Blankmandblankman@lternet.edu
<p>The current readme for Metacat 1.2 says: The build.xml file now has a <br />property named datafilepath. It should be set<br />to the location of where you want your data files stored. If you are an<br />existing user, this directory should be /<tomcatdir>/webapps/metacat/data<br />where <tomcatdir> is the your tomcat installation directory where<br />your webapps directory is located and 'metacat' is the name of your servlet<br />instance."</p>
<p>It should be changed to something like:</p>
<p>Your datafiles should not be stored in the /<tomcatdir>/webapps/metacat/ <br />path but somewhere else in order to prevent a webuser from access to stored <br />data. For unix users, the data directory needs to be writeable by whatever <br />user is running tomcat.</p> Bug #435 (Resolved): Source of problem with LTER metacat localizedhttps://projects.ecoinformatics.org/ecoinfo/issues/4352002-02-21T22:35:02ZDavid Blankmandblankman@lternet.edu
<p>We have isolated the metacat problem to problems with the individual server <br />"space.lternet.edu". These problems surfaced after the computer was upgraded to Solaris 8 <br />(from 7). The problem is not Solaris 8 related, however, because a metacat installation on <br />another LTER computer is able to function. When the metacat installation was point to the ldap <br />server on space.lternet.edu, the metacat did not work to authenticate. It did work to do <br />unauthenticated searches.</p>
<p>I set up a Morpho to point to the metacat on lorax.lternet.edu <br />with a user: dblankman,o=unaffiliated,dc=ecoinformatics, dc=org. In this configuration the <br />full system worked.</p> Bug #432 (Resolved): Metacat error message when authenticating from Morpho to LTER metacathttps://projects.ecoinformatics.org/ecoinfo/issues/4322002-02-18T21:06:35ZDavid Blankmandblankman@lternet.edu
<p>[space: oracle] 124: Error creating pool of database connections in <br />MetaCatServlet.handleGetOrPost<br />Io exception: The Network Adapter could not establish the <br />connection<br />2002-02-18 13:54:59 - SessionIdGenerator: Created random class <br />java.security.SecureRandom<br />ldap authenticating<br />389dc=ecoinformatics,dc=org</p> Bug #404 (Resolved): Create "CNAMEs" for LTER metcat and ldaphttps://projects.ecoinformatics.org/ecoinfo/issues/4042002-01-23T19:24:46ZDavid Blankmandblankman@lternet.edu
<p>Create CNAMEs:</p>
<p>suggested names: ldap.lterknb.org or ldap.knblter.org,</p>
<p>metacat.lterknb.org or metacat.knblter.org</p>
<pre><code>ldap.lternet.edu (for new internal ldap <br />dc=lternet,dc=edu)</code></pre> Bug #403 (Resolved): LDAP and LTER personnel password synchronization problemshttps://projects.ecoinformatics.org/ecoinfo/issues/4032002-01-23T17:53:32ZDavid Blankmandblankman@lternet.edu
<p>Discovered that the the random password generator function in the new person entry script (entry <br />into sql server database and LDAP database) is actually being called twice. Need to fix this. <br />Currently the password entered into the database and the one emailed to users don't match.</p> Bug #366 (Resolved): Install & Test LDAP SSL Componenet for o=lter serverhttps://projects.ecoinformatics.org/ecoinfo/issues/3662001-12-03T18:00:38ZDavid Blankmandblankman@lternet.edu
<p>Need to reconfigure o=lter LDAP server to support SSL, also implement Hashed password for <br />password creation.</p> Bug #278 (Resolved): Install production o=LTER LDAP Serverhttps://projects.ecoinformatics.org/ecoinfo/issues/2782001-09-04T21:43:51ZDavid Blankmandblankman@lternet.edu
<p>INSERT push from LTER personnel database completed and tested.<br />UPDATE push from LTER personnel database programming logic completed. Code <br />needs to be written and tested.<br />SECURE configuration needs to be implemented.<br />REFERRAL mechanism needs to be tested.<br />TARGET completion date: 10/1/2001</p>