How do I configure authentication for Canvas Catalog?
As a Catalog admin, your institutions allows you to manage multiple authentication methods for login. This is done through a secure, self-service admin user interface (UI).
Catalog admins can:
- Display multiple authentication providers
- Replace the Canvas Discovery page with a fully integrated Catalog-native experience
- Customize button labels and instructional text for each login path
- Preview and publish changes in real time, without developer assistance
- Enforce access to the settings through a new permission
- Maintain audit trails with full logging of changes in the Audit Log
This allows you to align the Catalog login experience with all identity providers already configured in their Canvas instance. It eliminates the need for engineering involvement and replaces the legacy Discovery page workaround with a native, streamlined solution. The result is a more scalable, user-friendly, and maintainable login experience that aligns with institutional identity infrastructure.
Open Admin
Click the User drop-down menu [1]. Then, click the Admin link [2].
View Authentication Configuration
As a Catalog Admin, users with the Authentication Configuration permission enabled can configure authentication.
View Authentication Configuration Tab
In the Catalog settings drop-down menu, the Catalog Info tab displays by default. Click the Authentication Configuration link.
Manage Authentication Configuration
You can select Canvas default authentication or define a custom configuration by using the Authentication mode drop-down menu [1].
Canvas displays all identity providers already configured in the institution's Canvas environment [2].
You can:
- Select one or more authentication providers to display on the login screen
- Customize the button text and instructional messages for each provider
- Optionally update the default Canvas login label for clarity
You can preview the login screen to verify the user experience before saving [3], then click Save [4].
View Audit Logs
When saved, the updates apply immediately and are recorded in the Catalog Audit Log.
This feature supports both root-level and subcatalog-level configuration, ensuring flexibility for decentralized or specialized programs.





