How site authorization works

To integrate Community Messenger with existing users' database and prevent unauthorized (hackers) access, all Flashcoms applications have a flexible authorization system. When an instance of an application opens, it calls the authorization handler which checks if a user is authorized. In return, the handler sends data in XML format.

If your site is Session/Cookies based then the handler uses the session/cookies user data to authorize.

If your site is not Session/Cookies based, you have an option to use UID (user identifier). You pass UID value to the application and it resends it to the authorization handlers to process the authorization.

The scheme below illustrates the calls sequence when a user opens a Community Messenger instance:

1. Javascript loads Flash client with following parameters: friendName, uid, langId, where:

friendName – required, receiver of the private chat request .
uid - initiator of the request ,required only with not Session/Cookies based authorization.
langId - if specified, the application automatically loads corresponding language.

2. Flash client loads settings from main.xml file and makes http request to the specified handler.

3. Handler returns xml formatted data back on Flash client query.

Integration steps

1. Add updater object as described in the corresponding section of the manual.

2. Specify handlers in the /settings/main.xml file.

3. Write the code for your updater and Community Messenger handlers following the guidelines described in handlers section of this manual.

4. Add chat links to the website.