krb5-wallet.git/perl/t/schema.t, branch release/0.10 Unnamed repository; edit this file 'description' to name the repository. https://git.gnuabordo.com.br/debian/krb5-wallet.git/atom?h=release%2F0.10 2010-02-09T21:06:31+00:00 Remove kaserver synchronization support from the wallet backend 2010-02-09T21:06:31+00:00 Russ Allbery rra@stanford.edu 2010-02-09T21:06:31+00:00 urn:sha1:59455fd5e6a47a66a2a84779f42928fd66ec9747 Remove kaserver synchronization support. It is no longer tested, and retaining the code was increasing the complexity of wallet, and some specific requirements (such as different realm names between kaserver and Kerberos v5 and the kvno handling) were Stanford-specific. Rather than using this support, AFS sites running kaserver will probably find deploying Heimdal with its internal kaserver compatibility is probably an easier transition approach. Remove Subversion Id strings 2009-06-09T21:39:39+00:00 Russ Allbery rra@stanford.edu 2009-06-09T21:39:39+00:00 urn:sha1:574a9c0456c182831b3d01a4d7ee0c737b91b107 Add file object support to the wallet server. 2008-02-09T01:57:42+00:00 Russ Allbery rra@stanford.edu 2008-02-09T01:57:42+00:00 urn:sha1:b415b347328e7db0f41f0294c06060c6dd156b3d Fix the module inclusions. 2008-01-23T20:11:11+00:00 Russ Allbery rra@stanford.edu 2008-01-23T20:11:11+00:00 urn:sha1:61d48fd55da2f533df4020b7130d58e6104aadbc Determine the class for object and ACL schema implementations from the 2007-12-05T01:10:23+00:00 Russ Allbery rra@stanford.edu 2007-12-05T01:10:23+00:00 urn:sha1:c0c34051887d08a94221f9cbc2b74fbfad34c22c database rather than a hard-coded list and provide Wallet::Schema methods for adding new class mappings. Add a missing class mapping for the netdb ACL schema verifier. Add a MySQL method to check the tables remaining after a drop. 2007-12-01T03:17:44+00:00 Russ Allbery rra@stanford.edu 2007-12-01T03:17:44+00:00 urn:sha1:9820080ca9470ffd1992430fc2842c2779839053 Run the full schema test with the configured database. It should work 2007-12-01T03:10:43+00:00 Russ Allbery rra@stanford.edu 2007-12-01T03:10:43+00:00 urn:sha1:9a6125ef765749841a766afbdea1b96b45c40e09 fine with MySQL. Actually use the username and password from the database configuration. 2007-12-01T01:14:14+00:00 Russ Allbery rra@stanford.edu 2007-12-01T01:14:14+00:00 urn:sha1:5500da38b3cbdb153453ace4a344b8c280927b3c The wallet backend test suite now supports using a database other than 2007-12-01T00:42:46+00:00 Russ Allbery rra@stanford.edu 2007-12-01T00:42:46+00:00 urn:sha1:c9948c8f68b11a1e897afe9c9f2dd2fcb6934f8d SQLite for testing. Also start a new Util.pm module for the test suite and move the contents sub into that module. More to follow. Initial work on supporting testing with MySQL. 2007-11-30T02:04:14+00:00 Russ Allbery rra@stanford.edu 2007-11-30T02:04:14+00:00 urn:sha1:1e13c0c60c96dd1719e7c4c3931b4196c2b5bc61 Add a drop() method to Wallet::Schema to destroy the wallet database. Add a test suite for it. Add a reinitialize() method to Wallet;:Server that drops the database before creating it. Modify the wallet object test cases to call reinitialize() to create the initial database and drop() to clean up the database after the test is complete. Fix a bug preventing Wallet::Schema from being initialized multiple times. We now stash the schema in a class static variable and reuse it for subsequent initializations, since re-reading DATA doesn't work.