Activity
From 05/05/2001 to 06/03/2001
05/29/2001
- 12:54 PM Bug #183: Port metacat to PostgresSQL and other databases
- I noticed that new classes that implement this functionality were checked in (by
Jivka). I have some file naming sug...
05/21/2001
- 03:42 PM Bug #190: modify resultset to return all package information
- Added ability to process multiple "returndoc" elements in
a pathquery document. Now, any query hit will be back trace... - 02:46 PM Bug #190: modify resultset to return all package information
- Modifications that change the package handling behavior of metacat. Package
membership is now determined by an identi...
05/11/2001
- 11:42 AM Bug #233: authentication always succeeds with empty password
- FIXED
- 01:46 AM Bug #160: need resource restriction capability
- Deferred indefinitely because SRB deployment is in question. Will reopen later
if we decide to deploy the SRB. - 01:45 AM Bug #152: Port SRB1_1_8 changes to Linux x86
- Deferred indefinitely because SRB deployment is in question. Will reopen later
if we decide to deploy the SRB. - 01:44 AM Bug #137: need admin client for managing SRB systems
- Deferred indefinitely because SRB deployment is in question. Will reopen later
if we decide to deploy the SRB.
05/10/2001
- 12:12 PM Bug #186: add web metadata entry form for Metacat
- Rudolf -- could you check in your current metadata HTML form and the perl script
that processes its contents so Chris... - 12:04 PM Bug #186: add web metadata entry form for Metacat
- Added cjones to cc list because he has agreed to work onthis as well.
05/09/2001
- 04:44 PM Bug #233: authentication always succeeds with empty password
- Fixed from Metacat
Ldap server seems to always allow access with empty password strings
05/08/2001
- 05:57 PM Bug #233 (Resolved): authentication always succeeds with empty password
- If logging into metacat, providing an empty string for a password always results
in successful authentication. This... - 11:47 AM Bug #199: changes in Access Control mechanism
- .
- 11:45 AM Bug #199: changes in Access Control mechanism
- 1. No changes are required for "public" access. Any LDAP auth server can hold
a "public" entry as a user or a group....
Also available in: Atom