Stand UniRubric up in your LMS in under thirty minutes.

Six steps. Copy-pasteable. LMS-neutral on this page; Canvas, Moodle, Blackboard, and Brightspace each get a short appendix at the bottom. No vendor call required.

LTI 1.3 · OIDC · JWKS · AGS · NRPS · Deep Linking 2.0

Demo C · 90 seconds

Architecture explainer in production. The configuration steps below are the canonical reference.

Sign up for an admin sandbox tenant

Sandbox tenants are fully isolated from production. You get admin-level access, the LTI 1.3 tool endpoints below, and a 100-run test budget — enough to handshake against your LMS test instance and grade a sample submission end-to-end.

Create admin sandbox →

Time: ~30 seconds · No credit card required

Add UniRubric as an LTI 1.3 tool in your LMS

Paste the configuration below into your LMS’s LTI tool registration. Most LMSes accept either a JSON tool config URL or manual entry of the individual endpoint URLs.

JSON tool config (option A)

Some LMSes (Canvas, Moodle 4) accept a tool config URL directly. Point your LMS at:

https://app.unirubric.com/lti/tool-config.json

Manual entry (option B)

If your LMS asks for individual URLs, use these. Everything below is public — no secrets in this config.

Tool name: UniRubric
Target link URI / Tool URL: https://app.unirubric.com/lti/launch
OIDC initiation login URL: https://app.unirubric.com/lti/login
Tool JWKS URL: https://app.unirubric.com/lti/jwks
Public JWKS method: URL (recommended) — rotates without LMS reconfiguration
Signing algorithm: ES256 (P-256)
Privacy: Public — UniRubric needs the launching user's id, roles, and assigned LMS context.
Custom parameters: (none required)
Required services: AGS (grade pushback), NRPS (names + roles), Deep Linking 2.0

Run the LTI handshake check

Once you’ve registered UniRubric in your LMS, run the check below. Unauthenticated, it reports whether our public endpoints respond as the LMS expects. Signed in to your sandbox, it adds deployment-level checks against your actual configuration.

Live verification

Run the LTI handshake check

Tests reachability of UniRubric’s LTI endpoints from the public internet. Signed-in users see additional deployment-level checks against their org.

Configure SAML SSO (optional, W17–W18)

Production SSO is currently in pilot with one institutional partner per the master roadmap. The metadata template below is the shape we’ll commit to once that pilot concludes. If you need SSO for your pilot today, email info@unirubric.com and we’ll provision a custom Microsoft Entra integration ahead of the general release.

<EntityDescriptor entityID="https://app.unirubric.com/sso/saml/{{ tenant }}">
  <SPSSODescriptor protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol">
    <AssertionConsumerService
      Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
      Location="https://app.unirubric.com/sso/saml/{{ tenant }}/acs"
      index="0"/>
    <SingleLogoutService
      Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect"
      Location="https://app.unirubric.com/sso/saml/{{ tenant }}/slo"/>
  </SPSSODescriptor>
</EntityDescriptor>

Status: template only · Production endpoint lands W17–W18

Configure SCIM provisioning (optional, W17–W18)

SCIM 2.0 user/group sync follows the same pilot path as SSO. The shape of the endpoint and supported operations is committed; the production endpoint goes live in W17–W18 alongside SSO. Until then, sandbox tenants are seeded manually via the admin UI or by request.

SCIM 2.0 base URL: https://app.unirubric.com/scim/v2/{{ tenant }}
Supported operations: GET/POST/PATCH /Users · GET/POST/PATCH /Groups
Authentication: Bearer token issued from the admin sandbox at Step 1
User schema extension: urn:ietf:params:scim:schemas:extension:enterprise:2.0:User (department, manager)
Group schema: Standard SCIM 2.0 Group; UniRubric reads display, members, and externalId

Status: schema committed · Production endpoint lands W17–W18

You're done

That’s the full integration surface. From here:

→ Lecturers in your org launch UniRubric directly from inside their LMS assignment — Speedgrader tab or equivalent. No extra login.
→ Grades and feedback push back to the LMS gradebook via AGS within seconds of the lecturer approving the release.
→ If you’ve wired SSO + SCIM, lecturer and student provisioning happens automatically. If not, lecturers self-serve from inside the LMS launch.

Need a hand?

Most institutions configure end-to-end without a call. If yours needs one, we’re a thirty-minute slot away.

Book a walkthrough