Microservices in the Brightspace Cloud
EduDentity Authentication Service
Download 120.79 Kb.
|
- Navigate this page:
- Feed Service
EduDentity Authentication ServiceDescription The EduDentity Authentication Service allows users to verify their identity, similar to the login process in Brightspace Learning Environment. This service is independent of any particular instance of Brightspace Learning Environment, allowing users to log in even if they are not associated with any particular organization. This service is used with products where users may not need to have any affiliation to a specific institution or implementation of Brightspace Learning Environment, such as Brightspace Binder. Location One global instance in Microsoft Azure South Central US and West US. Dependencies Depended on by Brightspace Assignment Grader Transcoding Service. Depended on by Brightspace Binder system, including the Brightspace Binder Data Store, Content Publishing Service (CPS), Binder Store, and Binder apps. Depended on by MyDesire2Learn. Depended on by Open Courses.
For each user registered in the system: A programmatic identifier for the user such as User ID = 123. A hash of the password (but not the password itself to prevent decryption). A security question and three hashes for the answers (but not the answers themselves to prevent decryption). Email address. First name, last name, and display name. The date the user was created. Whether or not the user has been verified and the deadline for verification. Whether or not the user is currently active and the date of deactivation (if applicable). The last successful login date, the number of failed login attempts, and the date the user was locked out (if applicable). Whether or not this is a dummy user and an expiry date (if applicable). How the Service Works
19.Alternatively, a separate solution requests the security question of the service. The response is checked against the stored hashes. Feed ServiceDescription The Feed Service provides an API for learner updates to the Announcements, Grades, and Content tools. It sends user notifications (the ones that appear in the minibar in Brightspace Learning Environment) to the Apple Push Notification Service (APNS) and Google Cloud Messaging (GCM) for use by the Apple iOS and Google Android platforms, respectively. Note When users log in with Brightspace Pulse, data starts collecting automatically. To prevent data collection while you are evaluating this product for your environment, disable the Feed Service.
A global cluster that resides in AWS. The Feed Service Database resides in IBM Cloudant. Dependencies Depends on the Authentication Service. Depended on by Brightspace Pulse.
The Feed Service stores Announcements notifications that are pushed from the LMS as they happen (in the LMS) for Brightspace Pulse users. This service itself does not return to the LMS to retrieve historical data. To communicate, devices and microservices use the HTTPS networking protocol. While in transit, all data is encrypted; however, data at rest is not encrypted. The user ID in data is a composite key along with the course offering ID; it is not a universally accepted global ID for the user. The user ID cannot be linked to a user's name or identity. In the database, user IDs appear as a series of repeated numbers. Regarding data retention, D2L requires the user ID to report on general user data; it is not used to report on the activity of a specific user. For example, the user ID may be used to report on how many users have an average of three or more dates per month. D2L would not use the data to report on how many times John Smith looks at his deadlines. D2L retains the data as long as required to generate reports based on general user data. The reports are subject to change at D2L’s discretion and client-specific data is subject to the terms specified in the MA, including data retention past contract termination.
Note The Feed Service does not transmit information from courses with an End Date that has passed or that have the Is Active setting disabled. How the Service Works
20.In Brightspace Learning Environment, events are generated that need to be sent to the Feed Service as push notifications, for example, an exam grade. 21.The event is stored in the Feed Service database. 22.The D2L Mobile Push Notification Service looks up the Device ID in the Mobile Push Notification Service Database to determine who the intended recipient is. 23.The D2L Mobile Push Notification Service sends the Device ID to the third party Push Notification Service (i.e. Apple, Google), which retrieves the event directly. 24.The 3rd party Push Notification Service sends a push notification to the device. No data is sent with the request, only a notice that information is available such as an exam grade.
Figure : How the Brightspace Feed Service works when receiving notifications in Brightspace Pulse Directory: ecat -> help -> browser -> documents documents -> Brightspace Platform Requirements 1 Document Change History 1 Brightspace Platform Requirements 2 Brightspace Apps 5 About D2L 9 help -> - documents -> Brightspace Platform Requirements 1 Brightspace Apps 4 About D2L 9 ecat -> The production of speech sounds 1 Articulators above the larynx ecat -> Connected speech and coarticulation Download 120.79 Kb. Share with your friends:
|
