Back
Account Protection and Credential Verification
I'm building my android app and I have a question about account security. Now I have a code construct in my application that checks if the email/password has changed. Q: When should it be used? I currently have the functions of changing my nickname, bio, email, password in the application. Should this be checked at all? Or is it easier for the user himself through the application to end the sessions of devices that are hacked after changing the credentials?
TL;DR
The user is asking about the necessity of a code construct to check if email/password has changed in their Android app. They are wondering if it should be used when functions like changing nickname, bio, email, and password are available. They also mention the option of allowing users to end sessions on hacked devices themselves. The user is seeking clarification on the best approach for account security.
Solution (if applicable): It is recommended to use the code construct to check if the email/password has changed when functions like changing nickname, bio, email, and password are available. This can help in detecting any unauthorized changes and provide necessary notifications to the user. Additionally
hi there, let's see. So, why would you be needing that code construct ? probably when:
- to store data when email password changes or updates (like when user changes their password and or their emil
- also you could run regular checks from time to time to see if their data might have been compromised.
- nickname bio might not be that much important i think?
- maybe setup email notifactions telling user that this this data has been changed and compromised and then user can confirm or deny whether it was them who made the changes
do you have confusions ?
if so, let me know and we can discuss this more
