ContextSDK Session Logout

Web Services can be used from a third party system to query back to the WebCT server to perform gradebook lookups/updates, read calendar events, send WebCT email, and perform other functions.

There is some risk associated with web service calls back into the WebCT server. Every web service call requires an active login session with the ContextSDK. This means that integrations should log out after performing the web service calls. If this is not done, it will result in an increased number of users in the system and could affect performance.

The risk can be mitigated by re-using ContextSDK logins for web service operations and then ensuring that the ContextSDK logout() method is called to release the login session. Some of the best integrations have used ContextSDK login pools to re-use login sessions.

This article originally authored by Scott Stanley on the WebCT DevNet