...or just someone who knows a lot more than I do.
Greetings...
I have a project in SE that is distributed network . There is a button on most screens that allows the user to open a dialog to edit current conveyor tracking information. The customer has requested that the button be protected by login security... no problem, right? Well, the problem is, if this dialog is opened (with proper login) on the SE server terminal, the same dialog also opens up on the SE client terminal (and vice-versa), which allows anyone at that terminal the ability to also edit the tracking info regardless of proper credentials.
So, how do I secure this type of configuration so that the credentialed user who opens the dialog (on either server or client) has exclusive editing abilities?
I apologize if this is an easy fix, but my vast experience is with ME PV+, so my knowledge of the inner workings of SE is a bit limited.
Kindest Regards...
Steve
Greetings...
I have a project in SE that is distributed network . There is a button on most screens that allows the user to open a dialog to edit current conveyor tracking information. The customer has requested that the button be protected by login security... no problem, right? Well, the problem is, if this dialog is opened (with proper login) on the SE server terminal, the same dialog also opens up on the SE client terminal (and vice-versa), which allows anyone at that terminal the ability to also edit the tracking info regardless of proper credentials.
So, how do I secure this type of configuration so that the credentialed user who opens the dialog (on either server or client) has exclusive editing abilities?
I apologize if this is an easy fix, but my vast experience is with ME PV+, so my knowledge of the inner workings of SE is a bit limited.
Kindest Regards...
Steve