Customer not able to log using my app
-
I am facing an issue where a customer cannot log from the app despite he can log to the account from a web browser (so not a password thing or a banned account of some sort).
The app has always been working with no complaints and has not needed any update for a long while.
So
Server.StatusOKisn't true for some reason
In the waiting and in the case someone can spot anything obvious I've missed, here's my login script:inline function login() { Server.setBaseURL(BASE_URL); Log.add("Reaching customer account...", "default"); Server.setHttpHeader(""); local parameters = {"username": usernameInputLbl.getValue(), "password": passwordInputLbl.getValue()}; Server.callWithPOST("wp-json/jwt-auth/v1/token", parameters, function(status, response) { user = response; Console.print(trace(response)); if (status == Server.StatusOK) { Log.add("Successfully connected", "success"); // do some UI actions... } else { connected = false; Log.add("Impossible to login...", "warning"); } }); }The user doesn't use any VPN or firewall. The location is Australia and I am waiting for more information about the macOS version, IP, and a more detailed log from my app.
The idiot I am forgot to add the status and response to the log...
-
@ustk Code looks good here.
@ustk said in Customer not able to log using my app:
The user doesn't use ... firewall
I doubt this is true and if it is then that's weird. Is he aware of MacOS built in application firewall? His router might also have a default firewall but I doubt that would block your app.
-
@David-Healey Mmm... Yeah I was thinking about third party FW set with rules that are too strict... But effectively the user might have changed the native FW rules! Checking this with him...
-
@ustk I don't know if this is still a thing (it used to be) - if his system clock is set different to current time it can mess with auth token validation.
-
@dannytaurus Thanks, so definitely a path to explore in the case the rest fails...