The Oxford University primary Single Sign On (SSO) username gives the owner access to a range of University and College on-line resources and beyond. It is never re-issued to anyone else once you have left.
This page documents the current process of issuing the SSO username and is primarily aimed at Card Administrators and Department and College IT Support Staff and gives fuller description than http://www.oucs.ox.ac.uk/registration/univcard.xml
An SSO username is only issued to people who have been confirmed by the Department or College as having a status which qualifies them for one. The status is confirmed by the issuing of a University Card by the Administrator for the Unit.
For what each status is entitled to, see Computing Entitlements. If you are entitled, you may be able to request additional 'project' usernames, to enable you to separate different roles eg Administrator, or for a publication or research project. These would be in addition to your primary SSO account, and could be transferred if you leave.
- For members of Congregation, the 'Invitation' to apply is sent by Card Office, and the application is returned to them directly.(Day 1)
- For other statuses eg Staff, the individual signs a paper application form and provides a photo. The form is then countersigned by the designated Card Administrator for the unit. (Day 1)
- Overnight a new record is added to the IT Services Registration database. (Day 2)
- The username is created (Day 2)
- Username data available to all units who need it. (Day 2)
- The letter containing the username and Activation code is automatically printed (Day 2)
- The letter is manually put in an envelope- usually addressed to the individual concerned. (Day 2)
- Neither the status of the person nor the course is available at the point of enveloping.
- The data is available for IT staff set a new Activation Code if they do not want to wait for the letter. (Day 2)
- If the individual has received their University Card, they can bring it to IT Services Help Centre to get their account details. (Day 2)
- The letter is collected by the University's Messenger Service about midday (Day 2)
- The letter arrives at the Department/College depending on internal post delivery times (Day 3/4)
Details Updated: existing person whose completion date has been extended
- Card Administrator informs Card Office by phone, email or paper that a person is still current in that unit. (Day 1)
- The Card record is updated, usually that day. (Day 1)
- IT Services Registration database is updated overnight (Day 2)
- The project times of all usernames belonging to that person are automatically extended. (Day 2)
- The validity of email addresses and TSM backup are also extended.(Day 2)
- No paper work is generated
Details Updated: existing or previous card holder whose affiliation changes
- Steps 1-2 above
- Data is added to IT Services Registration database (Day 2)
- IT Services automatically prints a list of all affiliation changes (Day 2)
- Affiliations are manually added or removed by IT Services Registration, based on the list. Changes often require expert local knowledge and are not easy to automate (Day 2).
- Email addresses are added and the old ones set to wind down over 2 months (Day 2). The owner is advised of expiring email addresses by email by an automatted process.
- Usually, no paper work is generated for the individual.
Where there is a Department, it will be used for
The College will be used for
For University members
- Electronic resources restricted to Members, including OXAM
- Central mail box
- Download software- Sophos, VPN, SPSS keys
- OxCORT undergraduate tutorial reporting
- Online supervision reports for Graduates(GSS)
- Staff and student access to Student Record system (OSS)
- Authenticated smtp: ie using
smtp.ox.ac.ukwhen you not on the Oxford network. See individual email client instructions and network documentation