Tools
Sign in
Login
Forum
Application Unlock
Forum
>
Administration & Deployment
>
Application Unlock
Christophe Suter
posted
on October 24, 2013
at 9:03 AM
Christophe Suter
posted
on October 24, 2013
at 9:03 AM
Hi
We have the feature lock/unlock application for deployment. Do we have an option to override the lock status by using a script? And if so, how?
Thanks!
Christophe
Thomas Suter
replied
on October 25, 2013
at 9:13 AM
Thomas Suter
replied
on October 25, 2013
at 9:13 AM
Hi Christophe
At the moment we do not have a script function for changing the application lock state. Could you describe your use case? Why do you want to be able to change the application lock state via script?
Christophe Suter
replied
on October 25, 2013
at 9:16 AM
Christophe Suter
replied
on October 25, 2013
at 9:16 AM
Hi Thomas
Use case scenario:
Application lock is set for deployment and the computer of the employee performing the export has a crash. According to our documentation, the lock is automatically released after the user's session has expired. But our client wants to have a fallback solution for this scenario.
Christophe Suter
replied
on November 5, 2013
at 4:10 PM
Christophe Suter
replied
on November 5, 2013
at 4:10 PM
Do we have any alternatives? E.g., manually expire a user's session?
Stephan
replied
on November 5, 2013
at 5:17 PM
Stephan
replied
on November 5, 2013
at 5:17 PM
Hi Christophe,
I checked the source code of Appway 5.2.3.10-dev. If I understand it correctly, the user which has locked the application should be able to logout and login again while the lock is still active. When the application is locked, Appway remembers the HTTP session id and the user id of the user requesting the lock. It grants access to the locked application in the context of the same HTTP session (matching HTTP session id) OR if the user has the same user id (matching user id).
Invalidating the user session does not help because the lock is not really linked to the user session. When the lock is created, Appway only takes the HTTP session expiration time as default timeout for the application lock. This does not mean that the lock is released if the user logs out or if the user's session is invalidated programmatically.
- Stephan
Christophe Suter
replied
on November 11, 2013
at 3:15 PM
Christophe Suter
replied
on November 11, 2013
at 3:15 PM
Hi Stephan
Thanks for your explanation!
It grants access to the locked application in the context of the same HTTP session (matching HTTP session id) OR if the user has the same user id (matching user id).
Does this mean that if a user Foo executed an application lock and performs a log-in from a different workstation, he is able to unlock it from this different workstation?
Stephan
replied
on December 16, 2013
at 10:15 AM
Stephan
replied
on December 16, 2013
at 10:15 AM
Yes, exactly. If it is not working like this, it is a bug.
Falk Lademann
replied
on April 7, 2014
at 10:45 AM
Falk Lademann
replied
on April 7, 2014
at 10:45 AM
Invalidating the user session does not help because the lock is not really linked to the user session. When the lock is created, Appway only takes the HTTP session expiration time as default timeout for the application lock.
The timeout for the application lock, as HTTP session is the default only, can this be configured somewhere then?
I can't find anything in the config with time or lock that would immediately lead to it.
What setting would I need to tweak to allow users to return and continue if they left the computer for lunch without saving, accidentally?
Please
sign in
to add a reply
About this site
|
Terms of use
|
Privacy statement
|
Contact us
© 2025 Appway AG. All Rights Reserved.
We have the feature lock/unlock application for deployment. Do we have an option to override the lock status by using a script? And if so, how?
Thanks!
Christophe