Sign on
Sign on (SO) occurs each time the desktop app starts. SO is preceded by a call to
baseurl.asp
, which returns XML that includes the Base URL that the client should use for sign on. This Base URL may be different than the Base URL specified during installation. SO operations are logged by the desktop app, and can be found by searching the desktop app log for 99=SO. The SO query string has the following format:
http[s]://<server_path>/csi/session/action.asp?99=SO&00=<UserId>&02=<Token>&03=<PID>&...
The following are query string parameters:
- 00: User ID.
- A negative VPS ID (for example, -2050329) indicates that this is a first time sign on.
- A positive value is for a User ID, and indicates that this is not a first time sign on.
- 02: Token, created by the system when the desktop app is associated with an existing user or when the system creates a user at sign on, and passed back to the app which stores it in the registry. Token is used during sign on to ensure that the desktop app associates with the correct user. Token, like userid, is unique for each desktop user and is stored with the user record in the database. The value for token at first time sign on is 0. The token is not displayed in theBlackBerry AtHocmanagement system.
- 05: Windows username.
- 06: Domain name.
For more information on query string parameters, see Appendix B: Desktop client URL parameters.
To prevent transmission of the machine IP, enable the
Collect Workstation Info
option in the BlackBerry AtHoc management console, at Settings
> Desktop App
.User creation
When the desktop app connects for the first time, the server attempts to find an existing user based on the selected authentication method and the query string parameters passed by the desktop app. If a user is not found, a new user is created. You can disable user creation in the BlackBerry AtHoc management console, at
Settings
> User Authentication
.