In order to authenticate over the SSH into the DataSpace, OAR, and Theses servers, one must request and obtain separate, privileged *NIX accounts from the Office of Information Technology using a ServiceNow @ Princeton (SN@P) request. Further, RSA SecureID soft tokens for this separate account with must also be requested.
Once these are in place, one should have set a PIN for the RSA soft token, along with properly configured the mobile app. which randomly generates temporary access codes.
One should attempt to authenticate into the server using
ssh [my_privileged_account]@[email protected]
. When attempting to
authenticate, one will receive a prompt Enter PASSCODE:
. Please enter the RSA
PIN followed immediately by your current temporary access code in order to gain
access to the server.
Once on the EZProxy server, one should be granted access to multiple servers for the following:
- DataSpace
cisdr202l.princeton.edu
updatespace.princeton.edu
- Thesis Central
cisdrtc100l.aws.princeton.edu
cisdrtc200l.aws.princeton.edu
- Waiver DB
asoar301l.princeton.edu
asoar201l.princeton.edu
- Open Access Repository (OAR)
cisdr103l.Princeton.EDU
cisdr204l.Princeton.EDU
Each one of these servers can only be accessed with the account dspace
(e. g.
ssh [email protected]
) from the EZProxy server. The credentials
are shared using LastPass, and may be requested from
either @jrgriffiniii,
@kayiwa, or
@stephayers.
When we update packages, the dspace servers sometimes have trouble coping. Check dataspace.princeton.edu after running maintenance. If you see issues, SSH into gcp_dataspace_prod1 and rebuild the project:
sudo su - dspace
dsbounce
The production dspace machine connects to PostgreSQL on a GCP box. Local IP for that is 10.64.16.3
. You can use Cloud Shell access from Google Cloud's platform to restart the database if needed:
sudo service postgresql restart