3. Requesting use of a CUD interface

A request must be made for access to CUD via an interface. The procedure is to request personal access to the CUD Web User Interface, plus service access to other interfaces as requested initially or subsequently. The initial request for access must be supported by a signed terms and conditions of CUD access form returned to: Identity and Access Management Team, Systems Development and Support, University of Oxford IT Services, 13 Banbury Road, Oxford. You may also scan the form in and send it as an attachment to you request.

For people who have no access to CUD UI use the following email template replacing elements in <> with your details:

To: sysdev@it.ox.ac.uk Subject: Request for access to CUD UI Please supply access to CUD as follows: Name: <your name> SSO username: <your username> Unit: <Unit of the University with which you are affiliated> ITSS: Y/N Reason for access (required if not ITSS):
  • ITSS should be answered Y/N depending on whether you appear in the ITSS register
  • If you are not on the ITSS register you must provide a Reason for access - why you are requesting access, including the purpose CUD data will be put to

Once you have access to the CUD UI you can request access to an additional service interface using the following email template:

To: sysdev@it.ox.ac.uk Subject: Request for access to CUD interface Please supply service access to CUD as follows: Name: <your name> ITSS: Y/N Reason for access (required if not ITSS): ITSS Managers: Machine FQDN: Interface requested:
  • ITSS should be answered Y/N depending on whether you appear in the ITSS register
  • If you are not on the ITSS register you must provide a Reason for access - why you are requesting access, including the purpose CUD data will be put to
  • ITSS Managers is a list of members of ITSS with /itss principals (e.g. unit0001/itss) who should be given access to download kerberos principals or other credentials generated as a result of this request. At least one must be provided
  • Machine FQDN is the fully qualified network name of the server or service which will be using the interface, e.g. host.oucs.ox.ac.uk
  • Interface requested should be one or more of:
    • REST
    • SOAP query
    • SOAP push
    • SQL Push
    • LDAP query
    • LDAP push
  • If your request if for REST, SOAP query or LDAP query and GSSAPI+Kerberos authentication is not supported by the software which will be used to access CUD, please include this information in Interface requested

Up: Contents Previous: 2. CUD Interfaces Next: 4. Data attributes available