In a standard Cliqon system all people who can have access to the system are treated as users of the system and their details are recorded in the Collection called dbusers. For the majority of application purposes to which Cliqon has been used in the past, this definition works perfectly - business directory, classified advertising system and ecommerce system. However there is a collection of applications to which Cliqon has been envisaged, including accounting system and customer relationship management (CRM), where the need to record information about people has been identified, that do not require any access to the system. For that reason we have reserved the Collection name of dbcontacts for that purpose.
Before discussing aspects of the Users Collection in Cliqon, can we please remind you to cross reference this page with Configuration -> Access Control.
In a standard production instance of Cliqon, there is only one requirement to access the dbusers Collection and that is to define users who may access the administrative system. We see this task to be a high level task that will be performed by those with administrative access to the system and therefore the menu entry, entitled "Users" appears in the "Structure" Group and we visualize will be protected with a Read/Write/Delete Level of 90:90:90.
When you install the system, you will have been required to configure the minimum details for one administrative User. The details for this Administrator will be written to the database with a Hashed password. We are not aware of any mechanism to recover that password. Thus if the situation has arisen where this password is lost or forgotten, access to the system may be prevented. Our experience of this happening over the years with smaller and less active Cliqon sites suggests that this is a relatively common occurrence, so we had to provide ourselves and our users and developers with a mechanism to obtain emergency access. We do this by the following method.
When you installed the system, we encouraged you to review /config/config.cfg. We drew your attention to a subarray with the Key Site.Users. We recommended that you delete or remove the section. It contains the following entries:
site.users.0.c_group = "admin"
site.users.0.c_username = ""
site.users.0.c_password = ""
site.users.0.c_level = "90"
site.users.0.c_status = "active"
site.users.0.d_firstname = "Cliqon"
site.users.0.d_midname = "Admin"
site.users.0.d_lastname = "User"
site.users.0.d_langcd = "en"
site.users.0.c_email = "firstname.lastname@example.org"
When an administrative users enters their username and password at the login screen, the login Method interrogates the database and if the username and password matches, access is granted. However if there is no match but before generating a failure message, the Login process looks up entries in the Site.Users array and compares Username and cleartext password in the file.
Obviously this represents a potential security hazard, so the emergency entry should be introduced and removed once access can be setup via the database.
We need to provide the ability to list, add, edit and remove Users in all types of Cliqon system, however
Add and Edit
Configuring a User Registration system
The Cliqon production system supports a full user registration and management system. It is this, that is used to control access and manage users in the Cliqon.Com presentation and management site. As all aspects of the full user user registration system are part of a front-end system, we do not include the templates in the standard Cliqon production system. If you would like to see our Bootstrap 4 orientated templates, please visit the Modules section of the Cliqon.Com website.
Created with the Personal Edition of HelpNDoc: Benefits of a Help Authoring Tool