What is Sphere Engine?
Sphere Engine is a cloud-based data platform that is used to introduce learners to SQL and Python. Sphere Engine allows learners to collaborate on datasets provided by Multiverse to understand the syntax of SQL and Python before applying their learnings to a secure tool that is used internally within your organisation.
When will learners need access to Sphere Engine?
Learners must be able to access Sphere Engine by:
DBA & DIBD - Month 12
DF - Month 3
ADF & ADE - Flying Start
What access will learners need to Sphere Engine?
Please test the domain https://sphere-engine.com/ at your organisation to confirm it is allowlisted. If it is not, please work with your IT department to allowlist all subdomains and paths from the TLD sphere-engine.com.
Examples of subdomains allowlisting rules should cover:
sphere-engine.com:
containers.sphere-engine.com and *.containers.sphere-engine.com:
widgets.sphere-engine.com and *.widgets.sphere-engine.com:
In addition, allowlist static files served from d2z1clqsdoqn5s.cloudfront.net:
Apprentices will not need to create accounts with Sphere Engine and therefore Sphere Engine will not hold any apprentice data. Multiverse provides dummy data sets which are integrated into Sphere.
Why is allowlisting Sphere Engine different from other cases?
Sphere Engine containers host a cloud-based editor and can serve dynamic web applications created by coaches and apprentices. This entails:
Paths and query strings: All paths are possible, in addition to query strings used in GET payloads.
HTTP methods: Methods beyond GET are possible, e.g. POST, PUT, HEAD, and OPTIONS. Rules should also permit
WebSocket Secure: “wss://” is used to provide live updates of code execution.
Subdomains: Rules should allow subdomains that are 2 levels deep, such as 4e23dab1.widgets.sphere-engine.com. These subdomains are used to delineate instances of Sphere Engine projects.