CAS Service Registration Request

To submit a request, create a service request in ServiceNow, copy the Service Registration Request below, along with your responses, into the ServiceNow request, and choose “Identity & Access Management” as the assignment group.

On this page:

Required Information

  1. Registered Service Label

    A short name that will uniquely identify the service (limit 30 characters).

  2. Description

    A short description of the application and the target audience, including how user information - whether obtained from CAS, the user, or other sources -will be used by the application and who will have access to that information (limit 500 characters).

  3. Destination(s)

    URI(s) where a user will be redirected after obtaining a service ticket. If the destinations are not yet available, the service can be registered but will remain disabled until a destination is provided. All destinations must be protected by SSL.

  4. ID Format

    [Anonymous id or UNI]

    The format of the user identifier returned in the ticket validation response. An "anonymous id" is an opaque string of characters derived from a given UNI and service. The anonymous id is constant over time (the same UNI and service will yield the same anonymous id) but it cannot be translated back into the UNI. Anonymous ids can be useful in self-registration scenarios in which the user enters information that can be linked to the anonymous id, or in cases where all the application needs to know about the authentication is whether it was successful.

  5. Single Sign-On

     [yes/no]

    Should single sign-on (SSO) be enabled for this service? (See CAS SSO for a description of how single sign-on behaves in CAS.)

  6. Show CU links

    [yes/no]

    Should standard Columbia University links, e.g., "Admissions", "Schools & Departments", etc., be displayed on the CAS login page?

  7. Technical Contact

    Name and email address for a full-time Columbia employee who is knowledgeable about the technical aspects of the web application. The contact should have a UNI and Columbia email address.

  8. Administrative Contact

    Name and email address for a full-time Columbia employee who is knowledgeable about the technical aspects of the web application. The contact should have a UNI and Columbia email address.

  9. FERPA applicability

    [yes/no]

    Will the application handle either student directory information that can be restricted by a student or other student information that is universally protected by FERPA?

  10. FERPA compliance

    If the answer to the last item is yes, have you reviewed the application for compliance with Family Educational Rights and Privacy Act Regulations (FERPA)?

  11. RSAM review

    [yes/no]

    Has the application been reviewed by the University's Information Security Risk Management Program? Please note the RSAM registration number if appropriate.

Optional Information

  1. Affiliations

    A list of LDAP affiliations that should be returned in the ticket validation response. These can include information on course enrollment, CUNIX groups, alumni information, school affiliation, and faculty/officer/staff affiliation.

  2. Help URI

    An application-supplied help URI that is displayed on the login page.

  3. Help Label Text

    A label for the Help link (defaults to “Help”.) Limit 30 characters. If there is no Help URI, this label will be blank.

  4. Custom Image

    An image of 440x50 pixels that should be displayed on the CAS login page for this service. (Attach the image with your request.)

  5. Multifactor Authentication

    [none (default), required, or optional]