2. Using your own pre-installed user registration system through table manipulation

In this case you can fit your existing user database into your chat server. Glassroom is a flexible system and has lots of features that enables you to connect it to almost any user registration database system.

As you know, Glassroom uses two tables to authenticate users and store profiles ( see here ). This feature gives you more possibility to fit your database into chat server. Consider following situations :

Case A. Suppose users register in your registration system. They prefer to use one nickname and one password for chat and others parts of your system. But they don't prefer to show their real registration information in chat profile ( Suppose an old lady lying in her age ! ). In this case, you should use your existing main user table as authentication table and use another empty table as user information table. You must set "AutoAddInfo" flag in "glassroom.properties" file manually ( default is true ), that is Glassroom must create user information record for every user in authentication table on demand.

Case B. Suppose that you have a main user table and you want to use it for both user authentication and user information. In this case you must set the table name for both authentication table name and user information table name. If some of fields of Glassroom are identical to existing fields ( i.e. email field ) in data type and semantic, you can freely use them. For other fields that are not in existing user table  ( i.e. flags1 and flags2 ) you must insert new fields in table. Please note that if this change damages your existing registration system, you can not use this approach.

Note : If there is some restrictions in your database that prevent Glassroom from adding new records in database, you must make built-in accounts ( guest, _default, admin ) manually. In order to make these accounts manually you must go through these steps :

A. Make these accounts manually in your existing database and set random passwords for "guest" and "_default" accounts to prevent users from changing these accounts.

B. If  "Enable user database" in "Server Configuration" is set, turn it off.

C. Enter Glassroom control panel as admin.

D. Use "Server Control" page to turn the chat server off, then on.

E. Enter "Accounts" page and edit these accounts. Don't forget to set "USER IS AN ADMINISTRATOR" flag for admin, unless you can not enter Glassroom control panel again.