Child pages
  • IsisFAQ
Skip to end of metadata
Go to start of metadata

ISIS Single Sign-On Frequently Asked Questions

NOTE: This is a live, evolving document. Please check back periodically for updates.

What is this UCLA Logon ID?

The UCLA Logon ID evolved from the current Bruin Online Login ID. If you already have an BOL ID, that will automatically become your UCLA Logon ID.

There are, however, some important conceptual and policy differences between a UCLA Logon ID and a BOL ID:

Currently, if you obtain a BOL ID, you automatically get email and ISP privileges. Consequently, BOL ID's can only be assigned to those who are eligible for BOL email and ISP access.

The UCLA Logon ID is a pure authentication credential with no authorization implied. In theory, anyone who wants a UCLA Logon ID can get one. Any member of UCLA (anyone with a real UID) is eligible for a UCLA Logon ID. In addition, persons without a UID can obtain a UCLA Logon ID (note many campus applications/services may not be available to a UCLA Logon ID that isn't associated with a UID).

Who manages the UCLA Logon ID?

The Bruin Online Help Desk provides main support for the UCLA Logon ID account related issues.

How do I get a UCLA Logon ID?

Students will be automatically be prompted to create his/her UCLA Logon ID upon entering UCLA and using URSA.

Employees can sign up for a UCLA Logon ID via a self registration service via the Sign Up link from any ISIS login page.

I have a faculty who refuses to get a Bruin Online ID, what do I do?

We have heard that many faculty members associate BOL ID with BOL email. Since they don't use BOL, they don't see the reason to get an account just to access application X. However, the UCLA Logon ID is quite different in this respect. A UCLA Logon ID is in fact a common logon ID a UCLA member uses to access a variety of online campus resources:

  • A researcher will use the UCLA Logon ID to sign on to a variety of research applications such as InfoEd (grant management), RATS (animal research control), and BRAAN/IRB (human research control).
  • A faculty can use UCLA Logon ID to sign on to teaching applications such as class web sites, course management systems, and gradebook.
  • A UCLA Employees will begin to be able to access UC For Yourself and Bencom to manage HR and benefits information using UCLA Logon ID.
  • When reviewing financial transactions for her grant, a faculty has to sign on to PAN, UCLA's financial and payroll audit notification system. A PAN user can sign on using the UCLA Logon ID.
  • Anyone who uses common online services such as Parking and Travel Express will sign on using the UCLA Logon ID.
  • Within the next 2 years, computer labs throughout the campus should start to use the UCLA Logon ID to login users to the workstations (CLICC and a few other labs already do that).
  • Access to BruinOnline email, the campus VPN, and the campus wireless network, already requires a valid UCLA Logon ID

I heard that UID/PIN is going away. My application needs a user's UID to look up his/her record. If UID/PIN is going away, what do I do?

UID/PIN as a method of authentication is going away. However, the UID is not going away. The 9 digit UID will continue to be an important system identifier for a core UCLA member. We are simply discontinuing the use of UID/PIN as a mean for a user to log in.

ISIS will continue to return a user's UID to an application upon login regardless of the type of login ID he/she uses to login. Your application will not be impacted.

I have a bunch of students who are used to logging in using UID/PIN. What's going to happen?

We are making changes to a number of applications and processes to make the transition as smoothly as possible:

  1. URSA is being revamped to fully integrate with ISIS. It is also being updated to guide incoming students to create a UCLA Logon ID as soon as they enter the university.
  2. ISIS is being updated to help users to make the conversion from UID/PIN login to UCLA Logon ID login.
  3. AIS, CTS, and the Student Systems Workgroup are working to create a coherent workflow and user interface between the UCLA Account Management application (CTS), ISIS (AIS), and URSA (AIS) so that any student attempting to login after the rollout will be smoothly guided through a one time conversion process and be able to immediately begin using their UCLA Logon ID to login to applications. Since this migration process kicks off at the ISIS login page, applications do not need to make any programming modifications.
  4. AIS, CTS and the Registrar's Office are working to create common help desk support materials to:
  • provide consistent user support
  • enable each application's help desk to provide consistent user support on login related issues.

I am currently using ISIS to authenticate users. How will this new version of ISIS impact my application?

ISIS 5 has the same programming interface as the current production version of ISIS (ISIS 4). You will not need to make programming changes to use ISIS 5. However, there are a few non-programming updates and changes:

  • We will be contacting everyone to collect updated administrative, technical, and support contact information.
  • There is a new version of the ISIS admin tool.
  • We will begin to enforce tougher standards on the creation of test and production application ID's (more on this soon.)
  • If your application services primarily the student population, we will need your cooperation in customizing your respective ISIS login page to display UID/PIN to UCLA Logon ID conversion information.

There was an ISIS 4.3 Beta. What happened to that?

Last year, we released ISIS 4.3 into beta testing, with the intention to turn ISIS 4.3 over to production by May 2005. However, because of these coming changes, we held off the release of ISIS 4.3. Instead, we are implementing all of the feature updates outlined for ISIS 4.3 in ISIS 5.

What about the other login types currently supported by ISIS (QDB, OASIS)? Are they still going to be around?

Yes. ISIS will continue to support QDB and OASIS login. However, we expect those login types will have very limited use for only a few specialized applications.