Hello,
So I've downloaded the lastest beta and have noticed these changes but I still have some concerns. It's highly possible I'm just misunderstanding how this works...
Basically, I want all users to be forced to enter a password anytime they are transitioning from a "Not Connected" state to a connected state (whether offline or online). Currently I have the same issue as before:
1. User starts the application.
2. User is asked to enter said password.
3. User simply clicks "Cancel" and then "Refresh".
4. Said user is now online and was never prompted for a password.
Is there currently anyway to prevent this behavior? Can a user always be forced to enter a password when starting the app or toggling between online and offline states? My initial thought was that my current configuration would at least function as such:
1. User starts application.
2. User is prompted for a password.
3. If user fails to enter the correct password then the user can not enter a connected state at all (offline or online).
4. User attempts to reconnect to DB (online or offline).
5. User is prompted for a password.
6. Cycle repeats until the correct password is entered.
I hope that make sense. Thank you very much for your time and assistance! You guys really have a kick ass product here and I very much appreciate the support!
edited by SrtTuner on 7/3/2014
edited by SrtTuner on 7/3/2014
edited by SrtTuner on 7/3/2014
So I've downloaded the lastest beta and have noticed these changes but I still have some concerns. It's highly possible I'm just misunderstanding how this works...
Basically, I want all users to be forced to enter a password anytime they are transitioning from a "Not Connected" state to a connected state (whether offline or online). Currently I have the same issue as before:
1. User starts the application.
2. User is asked to enter said password.
3. User simply clicks "Cancel" and then "Refresh".
4. Said user is now online and was never prompted for a password.
Is there currently anyway to prevent this behavior? Can a user always be forced to enter a password when starting the app or toggling between online and offline states? My initial thought was that my current configuration would at least function as such:
1. User starts application.
2. User is prompted for a password.
3. If user fails to enter the correct password then the user can not enter a connected state at all (offline or online).
4. User attempts to reconnect to DB (online or offline).
5. User is prompted for a password.
6. Cycle repeats until the correct password is entered.
I hope that make sense. Thank you very much for your time and assistance! You guys really have a kick ass product here and I very much appreciate the support!
edited by SrtTuner on 7/3/2014
edited by SrtTuner on 7/3/2014
edited by SrtTuner on 7/3/2014