Metacat: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362003-04-18T18:32:17ZEcoinformatics Redmine
Redmine 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 #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 #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> Bug #187 (Resolved): test metacat on Windows NT/2000https://projects.ecoinformatics.org/ecoinfo/issues/1872001-04-09T19:26:12ZMatt Jonesjones@nceas.ucsb.edu
<p>Need to test the Metacat servlet on NT/2000, possibly using an Oracle DB that<br />runs on another host for the time being. Then test with Oracle on NT as well. <br />Eventually, when SQLServer support is enabled, will need to test against SQL<br />Server as well.</p> Bug #163 (Resolved): need data repository interface for metacathttps://projects.ecoinformatics.org/ecoinfo/issues/1632000-10-25T00:38:08ZMatt Jonesjones@nceas.ucsb.edu
<p>Recent discussions have indicated that the metacat server should shield client<br />interaction from the SRB and other data storage systems (e.g., http servers).<br />Consequently, we need a new architecture for passing data to, and getting data<br />from, the metacat server. The metacat server would then look at the address for<br />the data object and dynamically load an adapter class that handles communication<br />with the appropriate backend data system (e.g., SRB, http). This could be<br />implemented as protocol handlers, or otherwise. The SRB adapter will require<br />extensions to the current srb RMI server to allow for streaming data objects.<br />All adapters will need to make use of the authentication and access control<br />interfaces, so there may be a need to extend those interfaces. At a minimum the<br />SRB adapter will need to query the authentication interface to find out the<br />proper MCAT username and password to use (which might differ from the original<br />if there is a user proxy system set up).</p>
<p>This proposed architecture assumes that the bottleneck introduced by passing all<br />data through a few servers is negligible. the alternative is to connect clients<br />directly to the SRB RMI server, which opens up possibilities of new clients<br />causing metadata/data synchronization problems.</p> Bug #137 (Resolved): need admin client for managing SRB systemshttps://projects.ecoinformatics.org/ecoinfo/issues/1372000-09-22T22:13:30ZMatt Jonesjones@nceas.ucsb.edu
<p>Need an adminsitrative utility modeled after the srb admin utility for managing<br />the distributed srb network, users on the network, and resources on the network.</p>