This page contains information for IT Departments of companies that use our Online Testing System. This information is specific for testing stations. Administrators should follow similar guidelines but there may be additional or specific bandwidth requirements depending on the company.

First and foremost:
ALL TESTING SESSIONS MUST BE PROCTORED BY A REPRESENTATIVE OR THIRD-PARTY AGENT OF THE COMPANY

• The Online Testing System auto-saves the entire test session every 30 seconds.
• A stable internet connection is required. Recommended bandwidth per simultaneous test taker: 128 kbps down/64 kbps up.
  • We do not recommend using WiFi (or other forms of wireless internet) as the stability of such an internet connection can vary.
• We do not provide additional software to be installed on testing computers; Online Testing is administered through a web browser.
  • JavaScript must be enabled.
• Our domain, ramsaycorp.com, and our IP addresses, 72.77.3.242 and 50.197.59.129, on ports 80 and 443 must be unblocked.
• Additionally, we are using a CDN provided by CloudFlare to help distribute common JavaScript libraries. To use those, we require their domain of cdnjs.cloudflare.com to be unblocked.
• Minimum software versions of web browsers we support are as follows:
  • Mozilla Firefox Current Supported Official Releases
  • Google Chrome Stable Channel
  • Apple Safari Current Version
  • Microsoft Edge

  The site may or may not work on other browsers but we do not provide support in the event that something does not work.

• A minimum screen resolution of 1280×1024 (standard) or 1280×720 (widescreen) is required.
• We do not recommend nor do we support testing on iPad, Android tablets, or any other mobile device. We only support desktop and laptop computers with a keyboard and mouse.

For best compatibility, we recommend the Mozilla Firefox and Google Chrome browsers.

If testing using the Take a Test app, the test taker must be running the latest version (1709 or higher) of Windows 10 Professional, Enterprise, or Educational editions. This feature is not compatible with Windows 10 Home. For more information, like how to set up user accounts specifically for test taking, please see this article.

What is SSO?

Single Sign-On (SSO) is typically a enterprise-level service that allows companies to leverage the authentication system already used by their internal systems to be usable on external systems. This is accomplished by exchanging user information (logins, authentication state, other identifying attributes) between the identity and service provider. This allows companies to streamline their authentication process as the user only needs to log in once with a single set of authentication credentials.

When the user tries to access a Single Sign-On enabled site, the identity provider passes the user information to the service provider, who then grants the user entry.

Does Ramsay Corporation support SSO?

Unfortunately, due to how accounts and logins are set up in Ramsay Corporation’s system, we cannot support SSO.

SSO provides proof that a user is logged in, but not the ability to differentiate which access level is appropriate or which account(s) to grant access.

In a typical Single Sign-On setup, all users have the same set of functions available to them. Ramsay Corporation’s access levels allow companies the ability to follow the Principle of Least Privilege where you only need to assign the minimal amount of access for the administrators to do their tasks. This means access is explicitly assigned per administrator, and runs counter to the benefits of Single Sign-On.

Additionally, Ramsay Corporation allows you to create subaccounts to organize your administrators and test takers. Each subaccount is a fully featured account and can hold test credits, administrators, test taker results, and everything else the parent account could possibly have. A company could have a dozen or even hundreds of subaccounts to organize their regions, locations, or even test groups. This also means that a single organization would have to identify which account or subaccount to place their administrators, and this is also why Single Sign-On is incompatible with our organizational setup.