ONLINE HELP
 WINDEVWEBDEV AND WINDEV MOBILE

This content has been translated automatically.  Click here  to view the French version.
Help / Developing an application or website / User Groupware
  • Overview
  • How to?
  • Branching the User Groupware on an LDP directory without management of rights
  • Branching the User Groupware on an LDP directory with management of rights
  • Starting the application
  • Installing the application that uses an LDAP directory
WINDEV
WindowsLinuxJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadIOS WidgetApple WatchMac Catalyst
Others
Stored procedures
Overview
The LDAP protocol is increasingly used by the companies. The LDAP protocol is used to query and modify the directory services. For example, Active Directory of Microsoft provides LDAP access to its data.
In a company, an account and a password are assigned to the users by the "IT" manager.
This account and this password can be directly used by the User Groupware of WINDEV and WEBDEV, with ability to define specific rights.
Remark: User Groupware works with Active Directory. It does not work with openLDAP.
How to?

Branching the User Groupware on an LDP directory without management of rights

To branch the User Groupware on an LDAP directory without management of rights:
  1. On the "Project" tab, in the "Project" group, click "User Groupware".
  2. Enable the User Groupware.
  3. In the "Files" tab:
    • Select "Authentication from an LDAP directory or Active Directory". Select "Click here to enter the server parameters" and specify the characteristics of the LDAP directory.
    • Check "Login window only (no management of rights)". In this case, the User Groupware will create no data file. A supervisor will not be able to define the rights for the windows and for the pages.
When the application is started, the login window or page prompts the user to authenticate. If the user is saved in the LDAP directory, the application will start; otherwise, it will be closed.

Branching the User Groupware on an LDP directory with management of rights

To branch the User Groupware on an LDAP directory with management of rights:
  1. On the "Project" tab, in the "Project" group, click "User Groupware".
  2. Enable the User Groupware.
  3. In the "Files" tab:
    • Select "Authentication from an LDAP directory or Active Directory". Select "Click here to enter the server parameters" and specify the characteristics of the LDAP directory.
    • If necessary, uncheck "Login window only (no management of rights)". In this case, the User Groupware creates the data files for managing the users and the rights. A supervisor can define the rights for the windows and for the pages.
Case 1: User Groupware database empty. The LDAP database exists
An additional configuration must be performed when implementing the application:
  1. Connect to the application as Supervisor.
  2. Choose "Configure the groupware".
  3. In the management window of the groupware, in the "Users and groups" tab, click the "LDAP import" button. This button is located below the list of users.
  4. A window allows you to import all the users.
    import
    If you are not authenticated on the LDAP server (1st use for example), a login and password of an LDAP user will be requested. The selected LDAP user must have the rights to list the users of LDAP directory.
    Caution: depending on the LDAP strategies defined in Active Directory, import may be limited to 1,000 users. In this case, to remove this limitation, it is necessary to modify the LDAP MaxPageSize parameter. For more details, see https://support.microsoft.com/kb/315071.
  5. Click the "Import" button. The import is performed, all the LDAP users are displayed in the list of users.
    Note: It is advisable to give supervisor rights to a specific user and delete the existing default "Supervisor" user.
  6. You have the ability to assign rights to the imported users.
Case 2: User Groupware database already exists. The application connects to an LDAP database
Only the users found in the database of user groupware and in the LDAP database will be able to connect to the application (same logins for the users). The password to use is the LDAP password. The users not found in the LDAP database will not be able to start the application.
The rights can be managed by the users found both in the database of the groupware and in the LDAP database.
Note: Using an LDAP directory with rights management makes it easy to switch from LDAP mode to non-LDAP mode.. Simply check "Use an LDAP directory".

Starting the application

In automatic start mode:
Indicate the characteristics of the LDAP server in the "Files" tab of the User Groupware configuration window.
To get the name of the user, simply call gpwGetUserInfo:
Info("Hello " + gpwGetUserInfo(gpwInfoLogin))
In manual launch mode:
To use the LDAP directory, you need to open an LDAP session using gpwOpenLDAPSession before using gpwOpen:
gpwOpenLDAPSession("xx.mycompany.com", 389, 3, False)
gpwOpen()
To identify a user without opening the login window, use the following code:
gpwOpenLDAPSession("xx.mycompany.com", 389, 3, False)
IF gpwLogin("FP", "Password") <> gpwOk THEN
Error("Invalid user or password")
EndProgram()
END
WINDEVWindows

Installing the application that uses an LDAP directory

The parameters of the LDAP directory can be entered by the user when installing the application.
When creating the setup of the application that uses the User Groupware, check "Set the path of groupware files during setup" in "Database parameters".
When installing the application, a screen specific to the User Groupware will be displayed. This screen allows the person who installs the application to:
  • configure the location of the data files specific to the User Groupware
  • enable the history of connections.
  • enable user authentication via an LDAP directory. In this case, you will have to enter the address of the server, the port number and the LDAP version used.
Minimum version required
  • Version 18
This page is also available for…
Comments
Click [Add] to post a comment

Last update: 09/30/2024

Send a report | Local help