[UCCAP Home Page]
[UCCAP References]
[UCCAP Acronyms, Glossary]
UCCAP
The UC Common Authentication Project
Overview
The aim of the UC Common Authentication Project (UCCAP)
is to produce a UC Common Authentication System (UCCAS).
UCCAS will provide UC-wide strong authentication which will eventually
support a broad range of applications and services.
"Strong authentication" is a cornerstone for various network
middleware which is necessary to use
our network conveniently and securely -
"An Information Architecture for UC: Critical Building Blocks"
provides context and motivation for network middleware including
authentication.
The ultimate scope of UCCAP is quite large and envisions providing a
"network passport" for every UC faculty, student, and staff.
Passports issued at one campus will be recognized by other campuses
and can be used as a basis for access control, digital signatures,
and other uses.
History
A University Common Authentication Project
was proposed to the
Joint Operations Group (JOG)
in July 1997.
JOG was enthusiastic and an
Authentication Working Group
comprised of campus and UCOP representatives
was put together. During August-October 1997,
the WG did some technology demonstrations,
identified outstanding issues, and formed recommendations
for next steps.
The WG submitted its
final report to UCOP in October 1997.
The technology demo was generally successful and the report was
generally positive.
UCOP took input from JOG on the report, did some analysis,
and made a report with recommendations to JOG
on January 28, 1998.
JOG was again enthusiastic and a second phase of UCCAP was pulled
together.
Current Work
This phase
is focused on certificate and Public Key Infrastructure (PKI)
technologies.
There are two (related) activities:
- Deployment of a limited production system supporting
real users for
specific applications;
- Continued analysis of open technical and policy issues
that will need to be resolved before widespread PKI
can be deployed.
It's a three-level effort:
- JOG/steering committee -
provides general oversight and direction and
allocates resources for participation in the next two levels.
-
Authentication Working Group - identifies open technical
and policy issues;
prioritize and analyze technical issues;
refer policy questions back to JOG for resolution.
Comprised of designated representatives from campuses, UCOP, and the
labs.
- UCCAP Implementation Team -
deploy a limited production system
including Public key Infrastructure (PKI),
University Directory, and participating applications.
Comprised of people actually working on certificate systems.
An implementation working area
serves as a
communication locus for people actively
working on UCCAP.
As such, it contains a lot of rough material and it changes
frequently.
[UCCAP Home Page]
[UCCAP References]
[UCCAP Acronyms, Glossary]
Send your questions, comments, and suggestions to
IR&C
Last updated January 28, 1999