Valence API Queries- Persist authentication/ user session/ asynchronous api call
Currently we are doing this way
For each and every API Call, we are authenticating the request and if the API retrieves the list of data with bookmark then we need to re-authenticate the URL with bookmark parameter again to get the data.
Is there any way that we could persist the authentication for that user's session instead of authenticating each API call, so that we can make different API calls without authenticating each and every time for every URL for the same user? If there’s any please share the code.
For now we created a common User ID/ Key for API call and we configured it in our customized application to access Valence API.
And manually we control the access for the OrgUnits by passsing the userid filter based on the logged in user id/ role. Instead we want to change in such a way that the API call should use the logged in users (User ID), so that based on his role the API will only list the orgUnits that he is enrolled, instead of passing the userid as the filter to the API.
But the constraint here is if we want to use the actual users, then we need to create the User ID/Key for all the actual users in the system manually one by one.
Is there any alternative or any other good way that D2l can authenticate the API call dynamically based on the user signed into eLearn application without having a need to create User ID/ Key for all the users?
Any example you can provide on how we can access the API call asynchronously using the D2l Dll provided by Valence API team?
- 48 views
- 1 version
- 1 reply
- 2 followers
- Posted By:
- sumathi ran
- February 16, 2017
About this forum
- 59,999 views
- 365 topics
- 24 followers
Ask questions. Share your expertise. Use this forum to ask or answer questions about the Brightspace developer platform - the Brightspace APIs, LTI, Remote Plugins, SDKs and tools.