School, district, and homeschool sign-in
Students should never share a campus password with a worksheet. Districts launch Abacadome from the LMS they already use. Homeschool families use a class code or parent code after a local account.
Unsigned “test” launches are rejected. Canvas, Brightspace, and Clever only create a session after a cryptographic check.
Canvas, Brightspace (D2L), Schoology, Moodle, ClassLink
These systems speak LTI 1.1. Your LMS posts a signed launch to Abacadome. We verify HMAC-SHA1, then map Learner → student, Instructor → faculty, Administrator → district admin. OSIBytes Group admins are never created this way.
- Launch URL:
https://abacadome.com/curriculum_api.php?action=lti_launch - Consumer key: issued per district (not published here)
- Status: LTI consumer is enabled on this host
Brightspace is the D2L LMS (sometimes called Brightway in district RFPs). Same launch URL.
Clever
Clever Instant Login uses OAuth 2. Abacadome exchanges the authorization code with Clever’s token endpoint and reads /v3.0/me. A bare ?code= with no Clever token is rejected.
- Redirect URI:
https://abacadome.com/curriculum_api.php?action=clever_login - Status: Ready — enable after the district adds Abacadome in Clever
Homeschool and small classes
- Parent or student registers at register.html ($75/year or a license key).
- Teacher creates a class and shares the class code.
- Parent links with a student / parent code on Connect.
- Teachers can also add a student manually from Faculty Command Center.
FERPA
Roster email from the LMS becomes the campus login. Quizzes and submissions stay behind a signed-in campus plan. Public lab pages do not include answer keys. Questions are served only after login + active plan.