Metacat: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362002-04-08T21:21:34ZEcoinformatics Redmine
Redmine Bug #465 (Resolved): Data diretoryhttps://projects.ecoinformatics.org/ecoinfo/issues/4652002-04-08T21:21:34ZJing Taotao@nceas.ucsb.edu
<p>Now if the Metacat doesn't have permssion, it could not create the data <br />direcotry automaticly. Uer should create the data directory and change it <br />permission manually.</p>
<p>We should let it created automaticly.</p> Bug #452 (Resolved): Configure ssl in dev and ecoinfohttps://projects.ecoinformatics.org/ecoinfo/issues/4522002-04-02T19:00:43ZJing Taotao@nceas.ucsb.edu
<p>We already configured ssl in local machine (Tomcat standalone). Now we need to <br />configure dev and ecoinfo. But in these machines, apache is the web server and <br />need more configuration than tomcat standalone.</p> Bug #449 (Resolved): Enable ssl for metacat and morphohttps://projects.ecoinformatics.org/ecoinfo/issues/4492002-03-26T21:27:15ZJing Taotao@nceas.ucsb.edu
<p>Now communication between Metacat and Morpho uses plain text. In order to <br />increase security, we want to enable SSL.</p> Bug #444 (Resolved): Create a JUnit test framework for MetaCathttps://projects.ecoinformatics.org/ecoinfo/issues/4442002-03-14T17:56:54ZJing Taotao@nceas.ucsb.edu
<p>JUint is powerful test tool and we need apply it to MetaCat. The first step is <br />to create a framework for it. The tasks include:<br />1. Revise build.xml and add a target named "test". When devopler type "ant <br />test", the JUnit test classes will be excuted.<br />2. Create a file stucture to store the test classes.<br />3. Write a simple test class to run.</p> Bug #437 (Resolved): Document Access Control Ruleshttps://projects.ecoinformatics.org/ecoinfo/issues/4372002-02-26T19:28:17ZJing Taotao@nceas.ucsb.edu
<p>Now the rules for document access control in Morpho and MetaCat are:<br />1. If a data package doesn't have access control list, the owner of <br />datapackage will be the only full control.<br />2. If a data package does have access control list, apply it.<br />3. If a member document of data package doesn't have access control list, <br />access control of data set document will apply to the member document.</p>
<p>The third rule is no good and need to get rid of it.</p>
<p>The reason is:<br />If a package smith.23.1 has a triple to point smith.34.1 and smith.34.1 <br />doesn't have access control list. It is okay because they all belong to a <br />owner - Smith. If another package named henry.2.1 has a triple to point <br />smith.34.1 too. Because smith.34.1 doesn't access control list and henry can <br />access it. Maybe henry doesn't allow to access it.</p> Bug #436 (Resolved): Bug of MetaCat in handling permission issuehttps://projects.ecoinformatics.org/ecoinfo/issues/4362002-02-22T21:05:57ZJing Taotao@nceas.ucsb.edu
<p>After login the metacat from that web page by using <br />"uid=tao,o=NCEAS,dc=ecoinformatics,dc=org" as username, the data packages were <br />gotten correctly. If delect the url and type <br />"dev.nceas.ucsb.edu/tao/servlet/metacat?action=read&docid=mike.4.12". Though <br />we are not the data package's owner, we can read the document in the browser <br />even the principal value in document access permission is not public.</p>
<p>It seems Metacat have some bug in access control in document level. For <br />exmaple, read the document directly.</p> Bug #408 (Resolved): Authentication is by-passed when a client follows an LDAP referralhttps://projects.ecoinformatics.org/ecoinfo/issues/4082002-02-01T22:29:21ZChris Jonescjones@nceas.ucsb.edu
<p>The ldap.ecoinformatics.org LDAP database services the dc=ecoinformatics,dc=org <br />tree, but is extended by LDAP referral objects that point to external LDAP <br />servers (e.g. dc=lter,dc=ecoinformatics,dc=org and dc=piscoweb,dc=org). When a <br />client (Morpho or web client) attempts to authenticate against ldap (via <br />metacat), if the user exists in one of the referred trees, authentication will <br />succeed, whether the password is correct or not. If the user entry is within <br />the main dc=ecoinformatics,dc=org tree, authentication will correctly fail if <br />the password is incorrect.</p> Bug #398 (Resolved): error in handling '&' in response to querieshttps://projects.ecoinformatics.org/ecoinfo/issues/3982002-01-15T04:49:23ZDan Higginshiggins@nceas.ucsb.edu
<p>There appears to be a problem in how Metacat handles entities like '&' in<br />responding to queries. If a data file name contains a '&' that gets encoded into<br />the triple linking the datafile to the datapackage. It get encoded as '&' in<br />the text, but when one looks at the response to an 'squery' the triple shows up as</p>
<p>"><subject>higgins.498</subject><relationship>isDataFileFor(96l</relationship><object>higgins.497</object></triple><triple><subject>higgins.498</subject><relationship>&</relationship><object>higgins.497</object></triple>"</p>
<p>actually, the relationship should have & after the "(961..." <br />Apparently, entities are not created when characters like '&' are pulled from<br />the database as the result of an 'squery'</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 #364 (Resolved): create OBFS interface for metacathttps://projects.ecoinformatics.org/ecoinfo/issues/3642001-12-01T01:22:39ZMatt Jonesjones@nceas.ucsb.edu
<p>Agreed to produce an OBFS interface for metacat that parallels the NRS interface<br />but is branded for OBFS. Target is Jan 2, 2002.</p> Bug #332 (Resolved): hub replication featurehttps://projects.ecoinformatics.org/ecoinfo/issues/3322001-11-29T22:09:23ZMatt Jonesjones@nceas.ucsb.edu
<p>Metacat replication is currently configured such that transfers are not<br />transitive (ie, if A replicates to B, and B replicates to C, the only data that<br />B will replicate to C is its own data). This is meant to prevent people from<br />having to set up extended trust netorks. This is a problem, however, for the<br />centralized access points that we designed for NCEAS/LTER.</p>
<p>At the annual meeting, we agreed that we need a special 'hub' replication<br />feature which enables a few special metacat servers to act as a virtual hub. <br />All data and metadata on one of these special hub nodes will be replicated to<br />the other hub nodes, regardless of its origin.</p>
<p>For example, if NCEAS and LTER metacats are the hub nodes, and NCEAS is<br />receiving replication data from NRS, and LTER is receiving replication data from<br />SEV, then all of the data would be replicated on both NCEAS and LTER hubs. <br />However, if the NRS metacat is getting data from a HAMILTON reserve metacat, the<br />NRS metacat will not replicate that HAMILTON data and metadata to NCEAS. This<br />preserves the trust relationship between NRS and HAMILTON, while allowing us to<br />create a virtual aggregation at the NCEAS/LTER hub. if HAMILTON wants its data<br />to show up on both the NRS and the NCEAS metacats, it will need to establish a<br />peering relationship with them both separately (e.g., HAMILTON -> NRS and<br />HAMILTON -> NCEAS).</p> Bug #329 (Resolved): groups ACLs do not work against LDAPhttps://projects.ecoinformatics.org/ecoinfo/issues/3292001-11-26T23:28:09ZMatt Jonesjones@nceas.ucsb.edu
<p>The use of a "group" principal does not work when the AuthLdap adapter is<br />working. This was traced to problems in the get Groups() and getUsers() methods<br />of AuthLdap.</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 #193 (Resolved): evaluate recursive search performancehttps://projects.ecoinformatics.org/ecoinfo/issues/1932001-04-09T19:47:43ZMatt Jonesjones@nceas.ucsb.edu
<p>Need to evaluate performance of recursive searches more thoroughly and, if they<br />turn out to be as fast as searches using the XML_INDEX table, then we need to<br />diable the use of the xml_index table.</p> Bug #41 (Resolved): consolidate methods for XML outputhttps://projects.ecoinformatics.org/ecoinfo/issues/412000-07-26T23:12:13ZMatt Jonesjones@nceas.ucsb.edu
<p>Create a set of utility methods for generating XML ooutput from the servlet.<br />This would include both normal output and error output messages.</p>