How site authorization works

Flashcoms products do not come with pre-built users' database as it was specifically designed to be integrated into existing website authentication mechanism and profile system. In case you don't have registration system on your website and need chat to work under integrated mode you may consider installing our free user's system which has basic attributes of a website and can be downloaded from your support area.

To integrate Video chat 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 videochat instance:

 

1. Javascript loads Flash client with following parameters: userName, roomId, langId, where:

userName - if specified, the parameter is passed on to the handler by GET method.
roomId - if specified, a user is forwarded directly to indicated room.
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 in accordance with enabled mode.

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