Parameters can be passed to the method to determine some properties of the session to create.
When invoked by a client application, Firmwater LMS will create/update the
A client application must be logged in with sufficient privilege and access rights to create/modify the passed in LmsPersonObject and, if specified, to register the user to receive the requested content (see CreateOrUpdate for further information).
Ordinarily, LMS users login manually from a login page. Upon authentication of the entered client ID, username and password combination, a user is granted access to an LMS session. Users with active LMS sessions are free to navigate through the LMS in accord with their security privilege and access rights. During the LMS session, users can then access learning content they are registered to receive.
An authorization token serves as a means of authentication into Firmwater LMS without requiring a client ID, username, and password combination. It is a globally unique identifier (GUID) representing authentication information for a single user, and can be thought of as the user's key to Firmwater LMS. Client applications must be aware that authorization tokens may expire. A token's validity period is controlled by Firmwater LMS administrators, hence, it is recommended that client application developers contact system administrators to determine the validity period of authorization tokens created via CreateUserSessionWithParams calls.
If an authorization token is a user's key, the authentication page can be thought of as the door the key unlocks. As part of the response to a CreateUserSessionWithParams call, Firmwater LMS returns a URL pointing to the authentication page that is formulated to automatically authenticate the user (using the authorization token) and forward them to the requested page. A client application need simply redirect the user to this URL.