Skip to content

Network Access Tokens Service

This page gives an overview of the Network Access Tokens service, describing its current status, where and how it's developed and deployed, and who is responsible for maintaining it.

Service Description

The Network Access Tokens site provides a site for Raven-authenticated users to obtain and manage per-device tokens allowing them to use eduroam and the University’s wireless network, and the VPN service.

Service Status

The Network Access Tokens service is currently live.

Contact

Technical queries and support should be directed to servicedesk@uis.cam.ac.uk and will be picked up by a member of the team working on the service. To ensure that you receive a response, always direct requests to servicedesk@uis.cam.ac.uk rather than reaching out to team members directly.

Issues discovered in the service or new feature requests should be opened as GitLab issues in the application repository.

End user support is provided by the Service Desk.

Environments

The Network Access Tokens service is currently deployed to the following environments:

Name URL Supporting VMs
Production https://tokens.uis.cam.ac.uk tokens-node1.csi.private.cam.ac.uk
tokens-node2.csi.private.cam.ac.uk
tokens-nodeq.csi.private.cam.ac.uk

Source code

The source code for the Network Access Tokens service is spread over the following repositories:

Repository Description
Application Server The source code for the main application server

Technologies used

The following gives an overview of the technologies the Network Access Tokens service is built on.

Category Language Framework(s)
Server Groovy 2.4.12 Grails 1.3.10
DB Postgres 10.5

Operational documentation

The following gives an overview of how the Network Access Tokens service is deployed and maintained.

How and where the Network Access Tokens service is deployed

The Network Access Tokens service application is deployed using RPM packages. These are built by Gitlab CI in the Application Server repository. These can be copied to the Bes RPM package repository run by infra-sas@uis by following these instructions. As a last resort RPMs can be manually copied and installed.

Deploying a new release

Once the RPM packages are added to the Bes RPM package repository running zypper in <package name> will install, if the package is an upgrade, zypper up should upgrade the package(s).

Monitoring

The Network Access Tokens service is monitored by nagios. There is also a status page that checks the various components of the service and returns 200 if everything is functioning normally.

Other documentation

Service Management and tech lead

The service owner for the Network Access Tokens service is Robert Franklin.

The service manager for the Network Access Tokens service is Rob Bricheno.

The tech lead for the Network Access Tokens service is Paul Badcock.

The following engineers have operational experience with the Network Access Tokens service and are able to respond to support requests or incidents: