| Author |
Users Management |
frangonve
Member
Posts: 110
Location: Madrid (Spain) until I can live at the beach
Joined: 18.06.08 |
| Posted on 16-08-2008 10:32 |
|
|
I'd like to have the option to add/delete users at runtime... Not just through the development environment. If an application with user control is developed and deployed, the users with admin level should be given the option to add/delete other users at the runtime settings dialogue box.
I'd like to be able to assign an event to open the runtime settings dialogue box.
Also I'd like to be able to protect different sections in the runtime settings dialogue box from different users/user groups.
Best regards
Francisco |
|
| Author |
RE: Hello |
vince
Member
Posts: 100
Location:
Joined: 30.01.07 |
| Posted on 16-08-2008 16:04 |
|
|
Yes
Could you not switch the design mode as an Admin and make some-kind of MULTIPLE user privilege....with MULTIPLE accounts undo a single unique ID...and then you can assign that PARALEL account to any new USERS at runtime...
It is probably closely linked to windows os aswell...privileges and accounts are designed or arrived at that way....could you not have the USER accounts on the WINDOWS OS and the machine itself?....so that without getting into windows...the user won't have access to the Limnor design or Limnor runtime....
V. |
|
| Author |
RE: macro |
vince
Member
Posts: 100
Location:
Joined: 30.01.07 |
| Posted on 16-08-2008 16:37 |
|
|
Hello
Yes
You can perhaps try making a MACRO program to achieve your desire. The MACRO feature of Limnor is able to IMPERSONATE any computer activity/interaction that any USER carry's out on the computer in question.
Limnor RECORDS then PLAYS back the HUMAN interaction that was recorded...in the MACRO program.
The MACRO records any interaction with the computer. The Window Manager performer is then able to CONTROL your chosen MACROS...at runtime....
The MACRO feature of Limnor's Window Manager performer can PLAY BACK those MACRO recordings you made...the AUTOMATIC NATURE of the computers operation is the result that you see...
Often a MACRO "chron job" will work behind the scenes...the working MACRO will be almost unnoticable...but it will be continually doing valuable work)
:-)
V. |
|
| Author |
RE: Users Management |
yw
Administrator
Posts: 670
Location: ***
Joined: 23.06.05 |
| Posted on 16-08-2008 18:30 |
|
|
Please try a new beta at http://www.limnor.com/downloads/limnor.msi.
A button was added to the runtime settings dialogue.
A new method, UserManager, was added to the Application performer. It can be used to create an action to open the user management dialogue. |
|
| Author |
RE: Users Management |
frangonve
Member
Posts: 110
Location: Madrid (Spain) until I can live at the beach
Joined: 18.06.08 |
| Posted on 17-08-2008 02:31 |
|
|
Thanks a lot!
I tried the new button at the runtime settings dialogue to add users and works flawlessly....
But I found a strange behaviour in the Log off button:
Step 1. If I start an application logging in as admin (username: admin) and I press F2, then I click on the Log off button.
Step 2. I get the User admin logged off message. I click the Ok button at the Log off window.
Step 3. From now on I can still use the application with no user logged in. (I expected the application being blocked until a user logs in).
Step 4. If I press F2 and I log in again, the runtime settings dialogue appears. (I expected to be able to use the application directly).
Step 5. At this point:
Step 5.1. If I click the Finish button the system logs me off and I arrive again to Step 3. (I expected the runtime settings dialogue to be closed and being able to use the application)
Step 5.2. If I close the runtime settings dialogue clicking the X button at the top right corner of the window, I remain logged in and I'm able to use the application as I expected from the clicking on the "Finish" button.
Cheers.
Francisco
Edited by frangonve on 02-01-2010 04:24 |
|
| Author |
RE: Users Management |
yw
Administrator
Posts: 670
Location: ***
Joined: 23.06.05 |
| Posted on 17-08-2008 13:52 |
|
|
We may disucss the behaviour design.
Step 3. the application will only lock the pages which have their "Security" property set.
Step 4. F2 will bring up the runtime settings if the application is not for design, for examples, the *.ezp file is read-only; the application is distributed to another computer by "Distribution | Application Distibute" menu. F2 will run the application only when the application is in design mode.
Step 5.1. the designed behaviour is to log off because normal application running does not require a user to log on until a secured page is accessed.
Edited by yw on 17-08-2008 13:53 |
|
| Author |
RE: Users Management |
frangonve
Member
Posts: 110
Location: Madrid (Spain) until I can live at the beach
Joined: 18.06.08 |
| Posted on 17-08-2008 15:39 |
|
|
Hello,
The above reported behaviour happened launching the .ezp file with double click from windows folder (read-only setting in .ezp file).
All pages in application and the Aplication performer had a "viewer" setting in Security property.
If I change the pages Security property settings to "Designer" then the login screen is not shown at start-up and the application runs with no user logged in.
Best regards
Francisco
Edited by frangonve on 17-08-2008 18:19 |
|
| Author |
RE: Users Management |
frangonve
Member
Posts: 110
Location: Madrid (Spain) until I can live at the beach
Joined: 18.06.08 |
| Posted on 20-08-2008 01:15 |
|
|
Hello dge,
I still think that user control is not working properly.
Yes, your statements are correct for application without security setting, in design mode and non secured pages.
But my application is secured (viewer level), in run mode and every page is secured (viewer level) and still is running with no user logged in!
Best Regards
Francisco |
|
| Author |
RE: Users Management |
yw
Administrator
Posts: 670
Location: ***
Joined: 23.06.05 |
| Posted on 27-08-2008 01:10 |
|
|
You are right. There was a problem here. Please try a new beta at http://www.limnor.com/downloads/limnor.msi. The new design is based on the idea that lauching the runtime setting should not change the current log on user.
Press F2, if the current user does not have the permission to launch the runtime settings then it asks for a new user log on. If a user with sufficient permission logs on then the runtime settings dialog appears. When the dialog closes the system returns back to the user before the dialog was launched. |
|
| Author |
RE: Users Management |
frangonve
Member
Posts: 110
Location: Madrid (Spain) until I can live at the beach
Joined: 18.06.08 |
| Posted on 27-08-2008 13:41 |
|
|
Hello and thank you for your attention.... I tried the new beta and The only difference i find is the lack or log off button.
But if a logged in user with enough level to invoke the runtime setting dialog clicks on the FINISH button, the user is logged off, the dialog window dissappears, and the application remains active and running with no user logged in, and so breaking the security rules...
Best regards
Francisco
Edited by frangonve on 21-12-2009 17:35 |
|
| Author |
RE: Users Management |
yw
Administrator
Posts: 670
Location: ***
Joined: 23.06.05 |
| Posted on 28-08-2008 00:08 |
|
|
Clicking the Finish button will not log off if the original user already has enough permission.
Suppose user1 logged in before launching the dialog.
If user1 has enough permission then the dialog appears. Clicking Finish, no user log off. The user is still user1.
If user1 does not have enough permission then a log in dialog appears to log in with a user with enough permission, suppose it is user2. The runtime settings dialog appears using permission of user2. Clicking Finish, user2 logs off and the user returns to user1. |
|
| Author |
RE: Users Management |
frangonve
Member
Posts: 110
Location: Madrid (Spain) until I can live at the beach
Joined: 18.06.08 |
| Posted on 28-08-2008 01:26 |
|
|
Hello and thank you for your help, 
I'll describe you my real life prototype:
An incidents recording application:
There are several security guards (viewers: user1, user2, user3 ) recording surveillance incidents:
They record them in an Access table (incidents table) thru a entry form and dispatch automatic email messages to several groups of receivers (receivers table) depending on the category of the incident (category table).
The incident record is timestamped and contains the identity of the guard, the category of the incident and a comment field.
And there is a supervisor (admin: supervisor) checking the incidents (viewing/editing/deleting records from the table).
As the guard shift ends, one guard has to log off and the arriving guard has to log in.
As far as I know currently the only way to do the shift change operation is shutting down the program and starting it again.
How can one user log off keeping the program protected until another user logs in?
Can be the log off method available to be used by performers (buttons...)?
Best regards
Francisco
Edited by frangonve on 28-08-2008 01:36 |
|
| Author |
RE: Users Management |
frangonve
Member
Posts: 110
Location: Madrid (Spain) until I can live at the beach
Joined: 18.06.08 |
| Posted on 28-08-2008 14:04 |
|
|
Hello,
Today I could test more deeply the log in/log off issue, and now i attached a logoff/login sequence to a button click event.
The problem is that after loging off and then opening the log in standard dialogue, if the user clicks the cancel button, the login dialogue window disappears and the application remains open and available with no users logged in.
Best regards
Francisco
Edited by frangonve on 28-08-2008 16:40 |
|
| Author |
RE: Users Management |
yw
Administrator
Posts: 670
Location: ***
Joined: 23.06.05 |
| Posted on 29-08-2008 23:09 |
|
|
I am trying to understand your sequence.
1. logging off, so there is no user logged in, right?
2. open the log in standard dialogue,
3. the user clicks the cancel button, the login dialogue window disappears and the application remains open and available with no users logged in
I do not see the issue here. At step 1, no user logged in, at step 3, it returns to the state of step 1 because the user clicks cancel.
|
|
| Author |
RE: Users Management |
frangonve
Member
Posts: 110
Location: Madrid (Spain) until I can live at the beach
Joined: 18.06.08 |
| Posted on 30-08-2008 03:04 |
|
|
Hello,
The problem is that being a protected application/page, it shouldn't be available if no authorized user is logged in. Only when an user types the right username/password combination he/she should be able to write/edit/delete (depending on his/her access level) records.
Best regards
Francisco |
|
| Author |
RE: Users Management |
yw
Administrator
Posts: 670
Location: ***
Joined: 23.06.05 |
| Posted on 30-08-2008 11:57 |
|
|
|
So, the problem is at the step 1 when it is a protected application. If no user logged in then the application should have closed. Right? |
|
| Author |
RE: Users Management |
frangonve
Member
Posts: 110
Location: Madrid (Spain) until I can live at the beach
Joined: 18.06.08 |
| Posted on 30-08-2008 16:28 |
|
|
Yes, that's it...
Cheers
Francisco |
|
| Author |
RE: log in and logging off any USER of an app |
vince
Member
Posts: 100
Location:
Joined: 30.01.07 |
| Posted on 30-08-2008 22:14 |
|
|
Hello
This log in and log off......issue is a long thread.
It reads like it is complicated.
Using common sense and thinking about a windows computer (same all over)
what every user always gets greeted with is a LOG IN screen....WELCOME
baring in mind how prolific this is as a feature of computing...
This thread is important. It is an important thing.
I tried understanding it......... but it is confusing.
When using any types of software programs on a PC machine you do NOT usually log in or log off from the application.
Why is it so complex?....such a simple feature of log on or log off from a Limnor application as a user?
Can not understand how this can be so complex?....in Windows machines you create as MANY user accounts of windows....as you want to USE the windows software APP......all those users must log or log out of the machine(s)...
This feature is what Limnor is tryig to achieve on it's applications?
The other alternative would be a HARD key lock of the machine(s) with a USB styled LOCK key...HARDWARE
Or the simple LOGGING in or LOGGING off from the actual Windows Machines that are in the buildings...
thanks
V |
|
| Author |
RE: Users Management |
yw
Administrator
Posts: 670
Location: ***
Joined: 23.06.05 |
| Posted on 01-09-2008 11:30 |
|
|
|
If the Security property of the Application and the first page is set to "Viewer" or "Desogner" then at Step 1 it will shut down the application if there is not a user log in. |
|
| Author |
RE: Users Management |
frangonve
Member
Posts: 110
Location: Madrid (Spain) until I can live at the beach
Joined: 18.06.08 |
| Posted on 01-09-2008 17:35 |
|
|
But it doesn't. After logging off, the application is available to everybody and clicking cancel in the login dialog too.
Best regards
Francisco |
|
