DubLabs’ turnkey managed solution consists of the app you create and publish, native integrations to your school’s systems and app management portal. Learn more about the native integration technology, Single Sign On approach and security features that make DubLabs’ platform stand apart.
The DubLabs integration server resides in DubLabs’ Virtual Private Cloud in Amazon. The DubLabs team configures and sets up the cloud-based environment for your school’s integration server. Mobile client access to your enterprise systems (AD/LDAP, SIS, LMS) is done through the integration server, meaning you don’t have to open these systems to the public internet.
The DubLabs server receives web service requests for services such as Login, Course Info, Directory, Notifications. Enrollment, Financial Aid and more from your school’s DubLabs mobile app. In turn, our integration server communicates with the school’s personnel directory (LDAP/AD) for authentication, SIS and LMS. Upon accessing the information, the integration server returns data specific to the request to the mobile app. The exchange of private information, including user IDs and passwords between the Mobile Client and the DubLabs Integration Server, uses standard SSL methods.
DubLabs uses several methods to authenticate app users to the app.
DubLabs supports two-factor authentication if it is required, and it is tied into your single sign-on system. The user experience is similar to regular SSO login except with an additional ‘send token’ screen after entering credentials.
When a user needs to access private features in the application (e.g., Courses), s/he must log in using their school-supplied credentials.
In summary, the DubLabs Integration Server takes the credentials contained in the request from the Mobile Client and compares them against either the LMS, LDAP or SIS, depending on the active configuration.
DubLabs does not store any user data. The Mobile Client relies on a secure HTTPS communication channel to the DubLabs Integration Server for authentication. A hashed User Id and Password are sent in the HTTP header for every private request to the server allowing the server to securely determine the requester and filter responses.
*Security questions were created and approved by the University of North Texas System IT Shared Services
For further information about the DubLabs’ Platform, accessibility, integrations, SSO and security may be customized in your environment, please schedule a call with our team.