Choose your setup guide
Public tool publishers configure optional shared sign-in in My Tools and do not handle client secrets. Tool owners install their integration; the CanDIAPL team maintains the portal services that complete enrollment.
CanDIAPL standards
Tool docs should follow Scientific Python conventions where practical, use NumPy-style docstrings for Python APIs, and publish stable documentation from public repositories when the tool is ready.
Shared sign-in publication settings
For hosted web apps, API services, and notebook web distributions, publishers may list optional CanDIAPL shared sign-in deployments. Keep Existing Access leaves the listing and current login behavior unchanged. Add CanDIAPL Sign-In keeps the tool's login available; Use CanDIAPL Sign-In Only selects CanDIAPL sign-in as the sole login.
Enter each exact HTTPS base URL prefix and its callback and logout URLs. Both redirects must remain on that origin and under the base path prefix. A deployment is available to all CADC-authenticated users; there is no group selector or per-user allowlist. Reviewers receive the full claims, capabilities, CADC access mode, and default-launch choice. Changes to those security settings require renewed review; changing only the deployment label does not.
The tool owner installs the integration once and completes automated enrollment through CanDIAPL. MMP does not collect or display client keys or secrets. Use the per-deployment enrollment status to confirm setup.
Download the shared sign-in adapter bundle and its SHA-256 manifest. The bundle guide covers Flask, Node/Express, OAuth2 Proxy gateway, and browser-only integrations.
Edit a tool publication