|
| WD14 - User groupware with HF/CServer |
| Iniciado por guest, 21,abr. 2015 11:22 - 1 respuesta |
| |
| | | |
|
| |
| Publicado el 21,abril 2015 - 11:22 |
I know this might be an old question. I Migrated my HF Classic to HFCServer. I Am still using the old HF Classic groupware.
I Know I must change it in the groupware configuration to HFCServer, I tried and I also looked at the example CS Groupware and i am still a little confused.
I Understand the groupware gets accessed before the application.
When using HF/C'S, why do i need to use groupware –can i not specify groups and right in the CCenter of HFCS, and then i have to write my own login etc.
Does the groupware have to have the same users loaded as the Server users
I want to identify each unique user name logged in on the server within my application, I dont want a group of user to log in as admin.
Can anyone please tell me what is the best practice for this, I am really interested in the most professional solution to use the groupware with client server, or has anyone a basic example.
I Would appreciate your expert opinions
Regards
Andre |
| |
| |
| | | |
|
| | |
| |
| Publicado el 21,abril 2015 - 14:03 |
Hi Andre,
The groupware allows two things: (1) Verify user credentials to give access to the application. (2) Allow fine-grained access to windows and controls in windows (read-only, grey, invisible, etc.)
The HFSQL C/S database users allows you two things: (1) Grant a connection to the database by validating the user credentials. (2) Allow fine-grained access to database files and allowed actions (add, delete, select, create, etc.)
Once you get that, you define what features you want to offer in your application. If you do not need fine-grained control on your application windows and fields, there is no point in using the groupware. If you do not need fine-grained access to the database, there is no point in using database user management.
On our side, we had a lot of difficulties in the past with the groupware and we developed our own solution for windows access. We use our own groupware which we control at 100%. And before WD20 the users' passwords were not ciphered or encrypted, which was not acceptable for us. So we had good reasons to manage all that ourselves.
For the database side we create a single "user" login for the application with the rights it needs. If later we want to provide specific access for ODBC, etc, we will create logins for these applications with allowed rights. But the application itself has one login and we validate the users ourselves.
Hopefully, this will help you in your decision making.
Best regards,
Alexandre Leclerc
Edit 1: Fixed typos |
| |
| |
| | | |
|
| | | | |
| | |
|