Username Usage in OLSA APIs

All username references must resolve to the same unique end user and you must adhere to that usage in all relevant OLSA APIs.

If the integrating application, LMS or Portal, uses OLSA Asset Integration, then any username argument passed through an OLSA API call must be the same value that passed in the core.student_id field of the AICC GetParam response from the same said application or the SCORM equivalent cmi.core.student_id. Ideally this value should be the LMS or Portal login ID or username for the learner in all cases.

For example, if the integrating application passes for the end user John Smith from the HR Group the value smith-123 for core.student_id, then you must use smith-123 to identify this same end user on all other relevant OLSA API calls.

The value of admin for the username argument is usually an incorrect usage.

Use the correct usage to ensure the following:

• Merging and reconciling of user tracking results between OLSA RO launches, and launches from other OLSA scenarios like OLSA S&L launch URLs or OLSA SignOn launch URLs, or OLSA Offline launch URLs.
• Proper entitlement management of content; this includes Courseware as well as Referenceware.