Additional Information and Clarification of String Trimming
This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.
The "String Restriction and Transformation" `discusses trimming leading and trailing spaces on user IDs and passwords and on meeting names and meeting keys. It also mentions differences between what the Live Meeting service API allows and what the Live Meeting Manager allows. The spreadsheet provides some additional clarification about these topics.
User "apiuser" |
Create user " leadspace" with password " leadspace" |
Through the API, successfully created user with this userID and password |
Through the Live Meeting Manager, was unsuccessful: Error "Invalid User Id format, User Id may contain letters and numbers." |
User " leadspace" |
General use |
Can execute API commands |
Cannot sign in to Live Meeting Manager using these credentials. |
User " leadspace" |
Through the API, create meeting " leadspace" with Keys " preleadspace" and " audleadspace" |
Successfully created meeting with this MtgID and Keys |
1. Cannot join this meeting using this MtgID/Keys from Join page. 2. If a meeting is modified through the Live Meeting Manager such as sending an invite, the MtgID is unchanged, but the leading space is removed from Keys; however, the meeting still cannot be joined because the Live Meeting Manager Join page removes the MtgID's leading space. |
User "apiuser" |
Through the Live Meeting Manager, create meeting " leadspace2" with Keys " preleadspace2" and " audleadspace2" |
ListMeetings reports that name=" leadspace2" and keys="preleadspace2" and "audleadspace2" |
Can successfully connect to a meeting from the Join page using either " leadspace2"/"audleadspace2" or "leadspace2"/"audleadspace2" |
In summary, the API allows some spaces that the Live Meeting Manager does not, and a meeting created by the API with leading or trailing spaces can have meeting names and passwords changed if that meeting is touched or modified by the Live Meeting Manager.
Our best practices recommendation is to not use leading or trailing spaces in user IDs, user passwords, meeting names (Meeting ID), or meeting passwords (Meeting Key).