This topic explains how to customize the routing between pages in Blackboard Learn. Your school can customize routing by uploading a custom login page to Blackboard Learn server (through the Customize Login Page link on the system Control Panel), or by implementing the requestAuthenticate() method on the HttpAuthModule interface.
The Customize Login Page function on the system Control Panel allows administrators to download a template for the login page and then upload a modified template to the server. This allows administrators to add extra script functionality to the login page hosted by Blackboard Learn.
Schools interested in customizing their Blackboard Learn login page must not remove the JSP tags on the page.
If users want to redirect to a login form on a page hosted by another application, instead of using the Customize Login Page function, they should implement the HttpAuthModule interface method requestAuthenticate() to do a redirect.
For authentication to function properly, any login form on a page hosted by another application must submit the form to the login broker at the Institution’s URL (for example, a login page hosted at “http://another.institution.com” must submit its login form to the URL “http://your.institution.edu/webapps/login”).
Redirecting to the Original Target URL
If a user has clicked a bookmarked URL that leads into the Blackboard Learn, but they are not currently authenticated, the application will route the user to the login broker URI with the originally requested URL preserved. The login broker expects that the rest of the application will preserve the originally-requested URL, in URL-encoded form, as either a hidden form variable or a query string parameter named new_loc. Any custom login page uploaded to the Blackboard Learn server, or any third-party script page that requestAuthenticate() redirects to, must keep this contract as well. If not, the Blackboard Learn will route to its default entry page.