Closed jrgriffiniii closed 2 years ago
I have finally found the breaking bug for this, apparently there is a broken Backbone.js
dependency:
This is not consistently present, and hence, I was struggling to understand why this was failing.
Using https://vpn.princeton.edu/https/pdc-discovery-staging.princeton.edu/
provided me with access over the VPN, while https://pdc-discovery-staging.princeton.edu/
was access-restricted. Hence, one should be able to access the API using https://vpn.princeton.edu/https/aspace-staging.princeton.edu/staff/api/
I have briefly confirmed that I am receiving a Palo Alto IP address for requests, so an additional range may need to be added for the ArchivesSpace staging server hosted by Lyrasis.
Using binding.irb
, one should be able to pass the Selenium Chrome driver cookies for the requests against the ASpace API.
This should be deprecated in favor of enquiring about this from Operations or the OIT.
This advances #12 by introducing experimental support for network authentication using
thor
andselenium-webdriver
for interaction using a web browser (there lies also attempts using themechanize
Gem). In order to address higher priority issues, this may need to be delayed before the first workshop session (this feature is not essential for the first workshop).