We've customized our catalog page quite a bit (in large thanks to this community.. you guys are awesome!) but we're running into an issue where our Login URL takes users to our college SSO login. (I guess this is default in Canvas). Our catalog will be used for non-domain users so we need the /login URL to redirect to _.instructure.com/login/canvas. Is it possible to customize this URL? Thanks in advance. Hope you all stay safe and healthy!
Solved! Go to Solution.
The only customizations to the login url in Catalog are to direct your user to a page after login. "<catalog_domain>/login?target_uri=/" would direct a user to the Catalog home page instead of the dashboard after login.
Catalog leverages whatever authentication you have in place in Canvas. If you have SAML as the default login method then your catalog users are going to be redirected to SAML to login to Canvas. Once the user is in Canvas, there is an OAuth workflow to log the Canvas user into Catalog. The workaround for this is to use a Discovery Page.
With a discovery page, all of your Canvas/Catalog users will be directed to select their authentication method before getting into Canvas (whether they are going through Catalog or not). This can be a minor disruption for your users, but shouldn't be too bad. For your institution, there would be a link to your SAML config (<canvas_domain>/login/saml) and another link to your Canvas login screen (<canvas_domain>/login/canvas). SAML users would click on the SAML link and be authenticated into Canvas/Catalog, and Canvas login users click the Canvas login link and login to Canvas. If they clicked the login button via Catalog, they will the be redirected to the Catalog target_uri (default is dashboard).
Hope that helps,
I was afraid you were going to say something like that. Our leadership is very hesitant making an institution-wide change unless we absolutely have to (especially given the shift to all students and faculty online right now). If there isn't any other way then I'll let them know and maybe they will reconsider or maybe we can find another store-front solution than catalog.
I appreciate everyone's help with this.
We are still looking into this issue with login on our Catalog page. Don't think we are ready as a new Canvas school to toss us a discovery page. What I am looking from others on this space, is if they have a separate instance for Catalog users. Our SAML login for our current faculty and students will be working normally. Our rep asked us if we would be interested in separate instance this way Catalog would be pointed to that and would stay all local users. Has anyone has this setup before and give some insight.
Any way to avoid an extra step in the purchase / login process would be fantastic so I'm open to a separate instance, but I'm not sure what is involved. We will also have institution people accessing content eventually so I'm not sure that will work for us unless it is easy to go between/back and forth between instances?
I'm glad to see this is not just an issue for us. Perhaps this can be addressed by the catalog team? Is this product still being actively developed?
That's understandable. We have a similar issue. Since our Catalog and Canvas instance are not tied to any SIS, I'm trying to come up with a way to pass information from the Catalog to the college system (ACEware in this case). I'm thinking an API may be able to handle the transfer of the information, but I'm not super versed in creating and running APIs, unfortunately.
In terms of passing information between the two instances, I'm not sure how that would work. It seems like it should be simple, but I'm guessing it's not. Hopefully someone who actually has two separate instances is able to add input.
I'm having a really hard time getting anyone to answer a question about Catalog on a support case. They have passed me off to different teams and closed the ticket twice now, all without answering my questions. It seems like there is very little manpower assigned to the Catalog.
We (University of Wyoming) have a separate instance for our Catalog users - our main instance uses SSO and is tied to Banner and our credit courses, while our other instance is not. We are hoping to tie in Elevate to it, in addition to manual course creation, but we don't have this set up yet.
We run the same setup with SSO on our Production Canvas system with Banner backend. Love to pick your brain on some questions as we are looking to move down a separate instance for Catalog users only.