|
|
|
|
|
|
|
|
|
|
- Overview
- The options of the User Groupware
- Implementing the User Groupware in your application
- User Groupware in the Linux sites
- Options of the "General" tab
- Integration mode of groupware
- Starting the User Groupware
- Automatic login in test mode
- Using an LDAP directory to authenticate the users
- "Files" tab
- Password of data files
- Enabling the history of connections
- Type of database
- "LDAP" tab
- Characteristics of LDAP server
The options of the User Groupware
 Warning
From version 18, the User Groupware evolves. This help page corresponds to the User Groupware kept for backward compatibility. For help on the new version of the User Groupware, see User Groupware.
An application is often intended to be used by several users connected via a network. Similarly, a site is always intended to be used by several Web users. In most cases, different access levels must be defined according to the user or to the Web user. To manage these access levels in your WINDEV applications or WEBDEV websites, simply include the User Groupware. In just a few clicks, a standard application can be transformed into an application that manages several access levels. This feature can be easily implemented. The options of the User Groupware Implementing the User Groupware in your application To implement the User Groupware in your application: - Select "Workshop .. Configure the User Groupware".
- Check the "Enable User Groupware management" option.
- Validate.
Options of the "General" tab Integration mode of groupware Two modes are available for including the User Groupware in your application: - Default integration:
The programming of the User Groupware is automatically included in your application.
A new window or page is integrated into your project: The login window/page. It is displayed when the application is started and it allows the user to connect to the application. You can customize this window/page by applying the skin template of your application for example. - Custom integration:
The programming of the User Groupware is automatically included in your application.
All the windows or pages required to manage the User Groupware (login and management of users) are automatically included in your project. You can customize all the windows or pages used by the User Groupware.
Starting the User Groupware Two modes can be used to start the User Groupware: - Automatic launch: The user groupware login window or page is launched before any other window/page of the application. The project initialization code is run when the login window/page is opened and validated.
- Manual launch: The login window or page will only be opened if the gpwOpen function is used.. This option is used to run the project initialization code before opening the login window/page. This option is useful, for example, in the case of a multilingual application: a window or page can be displayed to ask for the application's runtime language.
Automatic login in test mode Specify the login and password that will be used in automated test mode. This information will be used if an automated test is run on the application. Using an LDAP directory to authenticate the users If the company of your customer uses an LDAP directory, you can enable the User Groupware on this directory. Therefore, the account and the password found in the LDAP directory will be automatically asked to the user. Two modes are available: - No rights management: In this case, no groupware file will be created.. If the application is started in automatic mode, the user will need to log in. If the user is saved in the LDAP directory, the application will start; otherwise, it will be closed. A supervisor cannot configure the rights on the windows or pages.
- With rights management: Only users present in the LDAP directory can log in. The rights can be configured on the windows or pages.
Note: The User Groupware operates with Active Directory. It does not work with openLDAP. Password of data files By default, the data files found in the User Groupware have a specific password. This password is: "PCSGPW2001". To change this password, enter the new password. The characters typed are hidden. Note: This password is used, for example, when re-indexing files or opening files with the WDMAP tool. Enabling the history of connections If the history of connections is enabled: - An additional data file is created: GPW_LOGCONNEXION. This file contains the history of connections.
- When configuring the application, the supervisor can access the history of connections via the "History of connections" button.
This history is displayed in a specific window/page. This page is used to identify all the users who have been connected to a given application during a specific period. A chart indicates the number of connections per hour during the day. A button is available to clear the history if necessary.
Type of database The User Groupware handles several categories of files: - the data files used to identify the users. These users can use several applications. Therefore, these files can be shared among several applications.
- the data files used to manage the rights granted to the users on the windows or pages found in the application.
These files can be: - in HyperFileSQL Classic format (by default). You can specify the directory in which each category of user files (specific to the User Groupware) will be created and used for the test of your application.
- in HyperFileSQL Client/Server format. The characteristics of the connection to the HyperFileSQL server must be specified as well as the directory of the different categories of files.
Characteristics of LDAP server If the User Groupware was configured to use an LDAP directory, the LDAP tab is used to configure the characteristics of LDAP server used for test (and at runtime). The requested information is: - Server address
- Port number of server.
- Version of contacted LDAP server.
This page is also available for…
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|