- Notice: Undefined variable: token in bb_coveo_search_ui_block_page_attachments() (line 53 of modules/custom/bb_widgets/bb_coveo_search_ui/bb_coveo_search_ui_block.module).
- Warning: array_flip(): Can only flip STRING and INTEGER values! in Drupal\Core\Entity\EntityStorageBase->loadMultiple() (line 312 of core/lib/Drupal/Core/Entity/EntityStorageBase.php).
The Blackboard Mobile Web Services Building Block enables Blackboard Learn to communicate with Blackboard's mobile product line:
You must configure and register the Mobile Web Services Building Block to enable it on your system.
Configure and register the Blackboard Mobile Web Services building block
- On the Administrator Panel in the Building Blocks section, choose Building Blocks.
- Select Installed Tools.
- Locate Blackboard Mobile Web Services Building Block and access its drop-down menu.
- Select Settings.
- Select Server Registration Settings and edit the settings. Learn more about each setting.
- Select Approve to confirm the building block's privileges. The Building Block page refreshes and displays a message that the building block was made available to the system.
Server registration settings
|System Administrator Contact Email||Not used in the apps. (Deprecated)|
|End User Support Channel||Not used in the apps. (Deprecated)|
|End User Support Channel Label||Not used in the apps. (Deprecated)|
|Username Label||Label for Username field in default login page in the apps. Only for Native authentication mode.|
|External URL of Learn Server||This is the public URL of the Learn environment. Bb's registration service will use this to direct app requests to the Learn servers.
The external URL of Learn Server should not be set to an external authentication portal URL.
|User-facing URL||Not used in the apps. (Deprecated)|
|Name||The name that students and instructors search for in the mobile apps to find your institution.
To request additional search names, please reference this article on Behind the Blackboard prior to opening a support case.
|Environment Type||More on environment type|
|Authentication Type||More on authentication type|
There are four options for environment type: Production, Testing, Staging, and Development. Testing, Staging, and Development are all effectively the same. Under these configurations, the environment is only searchable through the Public ID within the apps. The Public ID is found at the top of the Mobile B2 Settings page. You can have as many Testing, Staging, and Development environments as desired. You can have only one Production environment unless otherwise specified in your contract. Production environments are searchable by the Name or the Public ID.
We recommend that you share the Public ID only with authorized employees for testing purposes. Blackboard reserves the right to change the Public ID at any time.
Only one production-mode registration is allowed per client ID by default. For co-production instances, please open a case with Blackboard Support.
The options for authentication type are:
- Native - which uses the Blackboard native challenge-response authentication system or LDAP, if one of those has been configured for the Blackboard Learn instance.
- Force to Web - which is the authentication type that handles custom or other authentication mechanisms that might be configured at your institution for use with all applications, including Blackboard. If this setting is checked, users are launched to the browser and re-directed to the institution's authentication page to login.
- HTTP Authentication - Deprecated – Use Force to Web
Blackboard Mobile does not have a separate authentication mechanism. The Blackboard Mobile Web Services Building Block, which provides the back-end server functionality for the Mobile apps, leverages the same authentication mechanisms that the institution uses for its Blackboard Learn instance. The two broad choices for the authentication mechanism are:
- Using the built-in Blackboard challenge-response authentication or LDAP (Native).
- Using a Web-based single sign-on mechanism for all applications throughout the institution (Force to Web).
How to point a Force to Web authentication type toward a custom external login page
This value can be configured under Blackboard Mobile Web Services Building Block > Settings > Change Mobile Login URL.
Generally, to find the recommended value, go to the default login page (/webapps/login/?action=default_login or /webapps/login/login.jsp). Copy the SSO provider link under Sign in with third-party account (do not open the link, use Copy Link Address). Please note that this configuration does not affect the login page for traditional web browser access.
If not using the recommended Mobile Login URL value suggested above, also note that sometimes it is not sufficient to simply point the URL at the external authentication portal if this does not automatically direct the user back to the Blackboard Learn instance. You may need a returnURL or some other parameter to direct the session back to the Blackboard Learn environment authentication endpoint.
If you have questions about configuring Force to Web authentication, please reach out to our Client Support team on Behind the Blackboard (available in English only).
Firewall allowed list to allow mobile traffic
Blackboard mobile products may require some modifications to your institution's network configuration (firewall/IP allowed list) to permit data to move between Blackboard Learn and Blackboard's mobile products.
Learn more about the firewall allowed list
The Blackboard Mobile Learn Central Registration System is a shared global cloud service that registers Learn instances and directs app client traffic to the appropriate registration. It's important to pick a search name that uniquely identifies your institution.
To prevent confusing search results, the registration system filters out common educational institution terms, such as: