OpenV*Secure Admin Database API Unit Test Description^{∗}

Jonathan I. Kamens

September 10, 1996

1 Introduction

The following is a description of a black-box unit test of the OpenV*Secure Admin Database API (osa adb). Each API function is listed, followed by the tests that shoud be performed on it.

The tests described here are based on the �OV*Secure Admin Server Implementation Design� revision 1.14.

2 osa adb get lock and osa adb release lock

Number: 1 Reason: A shared lock can be acquired. Status: Implemented

Number: 2 Reason: An exclusive lock can be acquired and released. Status: Implemented

Number: 3 Reason: A permanent lock can be acquired and released. Status: Implemented

Number: 4 Reason: Attempting to release a lock when none is held fails with NOTLOCKED. Status: Implemented

Number: 5 Reason: Two processes can both acquire a shared lock. Status: Implemented

Number: 6 Reason: An attempt to acquire a shared lock while another process holds an exclusive lock fails with CANTLOCK DB. Status: Implemented

Number: 7 Reason: An attempt to acquire an exclusive lock while another process holds a shared lock fails with CANTLOCK DB. Status: Implemented

∗/mit/krb5/.cvsroot/doc/kadm5/adb-unit-test.tex,v 1.1 1995/08/10 22:41:08 bjaspan Exp

Number: 8 Reason: An attempt to open the database while a process holds a permanent lock fails with NO LOCKFILE. Status: Implemented

Number: 9 Reason: An attempt to acquire an exclusive lock while a process holds a permanent lock fails with NO LOCKFILE. Status: Implemented

Number: 10 Reason: Acquiring a permanent lock deletes the lock�le. Status: Implemented

Number: 11 Reason: Releasing a permanent lock re-creates the lock�le. Status: Implemented

Number: 12 Reason: A process can perform a get operation while another process holds a shared lock. Status: Implemented

Number: 13 Reason: A process that is running and has opened the adb principal database can retrieve a principal created after the

open occurred. Status: Implemented, but not working