Accounting project....

James W DeRoest (deroest@cac.washington.edu)
Mon, 9 Feb 1998 10:42:45 -0800


Message-Id: <199802091842.KAA02210@mailhost2.cac.washington.edu>
From: "James W DeRoest" <deroest@cac.washington.edu>
To: "AST Webpage" <astweb@u.washington.edu>
Subject: Accounting project....
Date: Mon, 9 Feb 1998 10:42:45 -0800
In-Reply-To: <Pine.A41.3.95b.980206144303.16710K-100000@homer38.u.washington.edu>

-----Original Message----- From: Hugh Sheets [mailto:hugh@u.washington.edu] Sent: Friday, February 06, 1998 2:45 PM To: Internal Accounting Group; hornung@u.washington.edu; hugh@cac.washington.edu; ken@cac.washington.edu; pete@cac.washington.edu; remmers@cac.washington.edu; stenvik@cac.washington.edu; yonah@cac.washington.edu Cc: deroest@cac.washington.edu Subject: Accounting project....

Mike has done substantial work on the AVF client. See: http://daffy2.cac.washington.edu/avf/. This is not fully in production. This weekend, Sid's staff will upgrade AIX on Vitcos and also upgrade Informix. After the dust settles on these upgrades, Tom and Mike will move the AVF data into Shuksan and Mike's AVF client will go into production. The AVF will still exist on Austen for now, but will be pushed to Austen from Shuksan regularly so C&CI will not be editting the AVF on Austen.

Hugh, Tracy, Mike, Doris, and Mike Harrison met on Tuesday to talk about the web "who" client. There are some Campus folks who need access to the information who gives, have SecureIDs, but should not have access to student data. Tracy is working on creating two access lists for who. One authorizes access for Fac/Staff data, the other to Student data, and you would be in both lists if you need access to all data. Eventually, this control will be a flag in Shuksan that can be checked with an LDAP query.

Jim reported he made a li change so that all accounts (ids) that don't have a owner field set default to the owner being the "account" which is the encrypted SSN or SN, so all ids in li have owners.

Jim is using the Fac/Staff li files generated by Shuksan to load into li.

Pete still has a couple of bugs he is working out of web based new. This will be able to be modified for a "dawg license" which is simply a presence (id, password, email forwarding) in Kerberos without having a UA account. Note one will still have to be a UW person (in Shuksan) to get a "dawg license". More work involved before we will be able to handle affiliates.

Tom has removed some SVF processing from Austen's DAY1, 5, and 10 processes which have been replaced by Shuksan generated files.

Tom has been working on billing and expiration.

We reviewed the namespace plan and the key components of the highest priority: - Shuksan: the database is not finished, but is in production for some things. Tom is the key person. - LDAP server: not yet in production, but is high priority to get into service and publish the schema, even though it is under development and will no doubt change. Tom will put up an LDAP server and get the schema he has been working on on the web page. Hugh is trying to arrange a meeting with at least one of Ed Lightfoot's application programmers who we keep hearing needs to do LDAP queries ASAP. We would like to know specifically what sort of queries that want to make. - Kerberos KDC: Ken, Donn, and others are in the process of putting this in production and removing passwords from the local machines. - New/dawg license: Pete is almost done with new, dawg license can be done when defined. - tools: The necessary tools to access/administer the key pieces will be done as needed.

Important pieces one notch down on the priorities are MS Directory Services in parallel with our LDAP server and MS KDC in parallel with our KDC. We don't have NT hardware for this right now and MS KDC does not yet exist. Then there are the countless clients/billing/expiration/etc pieces we can see on the horizon but aren't there yet.

Task review: ------------ Tom: Database development, loading, processing. Faculty/Staff data loading, processing. LDAP server - publish schema, put up. DB2 for a test Informix replacement. Explore NT. AVF data loading, processing.

Pete: Web-based new.

Tracy: Work on entire suite of clients. "who" access controls

Hugh: Work on backup/restore policies. Arrange the removal of SVF.INFO on Austen. Arrange a meeting with Ed Lightfoot's application programmer.

Mike H: Review our list of known clients to be sure INFO's needs covered Make AVF handling web client.