Pamba, a worked example
Pamba, the Panhari learning platform, was the first conforming client of the integration contract, and the contract grew out of its integration. It is described here as a worked example, not a special case: nothing in Murmle behaves differently for it.
What Pamba does for each part of the contract
| Contract element | What Pamba does |
|---|---|
| Registration | issuer is Pamba's configured issuer URL; jwks_uri is https://<pamba host>/.well-known/pollinator-jwks.json; webhook_url is https://<pamba host>/api/v1/pollinator/webhook. The signing secret Murmle returns becomes Pamba's webhook secret. |
| Launch endpoint | Posts to {MURMLE}/api/v1/launch/pamba - pamba is just the log label. |
| Token | RS256 with a kid; a 60-second exp; a UUID jti; sub is the Pamba user id; email, name and roles (["instructor"] for staff, a learner otherwise); return_url back to the course player. |
| Claim names | Sends both resource_id and the legacy context: {course_id, activity_id}, with the same activity id in each. It sends neither context_id nor contract_version, so its context comes from the legacy context.course_id alias and it is read as contract v1. |
| Outcomes | Handles submission.completed: marks the lesson activity complete and, when max_points is greater than 0, writes a grade. Acknowledges and ignores every other event type. Idempotent on redelivery. |
Configuration on the Pamba side
Point Pamba at Murmle's public origin - everything, including the launch endpoint, is served from it:
POLLINATOR_BASE_URL=https://<murmle host>
POLLINATOR_ISSUER=https://<pamba host>
POLLINATOR_AUDIENCE=https://<murmle host>
POLLINATOR_PRIVATE_KEY=<PEM>
POLLINATOR_KEY_ID=pamba-launch-1
POLLINATOR_WEBHOOK_SECRET=<returned once when the integration is registered in Murmle>
What carries over to your own client
- Pamba needed no change when the contract was made product-neutral: every wire format it used
stayed accepted. It may adopt
context_idandcontract_versionat its own pace. - Its outcome handling is the pattern to copy: verify, deduplicate on
event_id, write a completion for unscored activities and a grade only when there are points, and return2xxfor everything it has finished with - including events it ignores.