Contact person: Business Client

Phone:Show

Email:Show

Location: Batley, United Kingdom

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"I need a quick, reliable way to cut off access to a private Android APK that I previously shared with three employees. Although I have already changed the password in my online control-panel, the app keeps authenticating with the old credentials.

Current setup
• The APK authenticates through a simple Username and Password check.
• It offers an update option, but only when the user taps “Check for updates.”
• I control the server, database, and API endpoints, so back-end changes are possible right away.

What I want to achieve
1. Immediate invalidation of every existing session, forcing the app to refuse the cached password and prompt for a fresh login.
2. A server-side tweak (rate-limit, token table, password-hash change—whatever is cleanest) so new logins succeed only with the new password.
3. A concise set of steps or code snippets that show me how to repeat this process any time I need to revoke access again.

Acceptable approaches
I’m open to adding a token system, expiring sessions in the database, pushing a small version bump that checks a flag on the server, or any equally solid method you recommend. The only hard requirement is that the three existing APK installations must stop working until I decide otherwise.

Deliverables
• Updated server/DB code or config that enforces the new credentials.
• (Optional) Minor APK patch if you believe client-side changes are essential.
• A short document explaining what was changed and how to roll it back or repeat it.

If you’ve tackled session invalidation or forced logout flows in Android/Java (or Kotlin) and back-end stacks such as PHP, Node, or Python, this should be straightforward. I’m ready to give you SSH/API access the moment we agree on a plan so we can wrap this up quickly." (client-provided description)