Hi, friends! I've been presented with an interesting challenge.
We call our portal and authentication provider (CAS) ACES. Occasionally, when someone wants to simply login to the portal, they google ACES Login. However, they don't get the portal - they get our Canvas instance because it automatically redirects to CAS - hence the title "ACES Login" on the google result. See the following GIF and notate the URL in google (alamo.instructure.com).
If I were to authenticate, it would complete the login process to Canvas, and not the portal which some people would be expecting.
Our Help Desk Manager reached out to PR to see if they could do some PR magic and push our portal to the top, but instead they came back with the fact that we needed to use the meta data in our Canvas login page to clearly identify what the page is for, and it would slowly trickle down.
Here are my fears and questions...
It's a redirect - what control do I have?
Can I actually access/update the meta data of the login page? If so, where?!?
Any help or insight you've got is GREATLY appreciated. Thanks!