Rank: Advanced Member
Groups: Registered
Joined: 5/23/2016(UTC) Posts: 129  Location: Virginia Thanks: 20 times
|
I have assigned users a username and password. I have set the server settings to use customized login and to allow login via mt/login. I have assigned the users the role of all, authenticated, and workflow user. I have set the permissions on the public folder.
When the user downloads the mobiletogether app, they reach the demo page and can add my server and put in the name, address, port, username and password and save it. when they try to access the server and download the solutions on my server, they are asked to authenticate, they put in their password and it is rejected saying wrong username or password continuously. However,
I can use their credentials on either of my two phones which have different ip addresses and walk right in to the server. I have had them to clear their browser cache but they still continue to have the same problem.
Please give details of what you think the problem could be. Hopefully, I have given the necessary information to assist.
Thanks,
|
|
|
|
|
|
Rank: Administration
Groups: Registered, Administrators
Joined: 12/2/2015(UTC)
Posts: 11
|
Please confirm if I understand the situation correctly. Both you and your user have a mobile device on which is installed the MobileTogether App. Both of you enter the same server details and authentication credentials. You, on your device, are able to connect, but your user, on their device, is not. Is this correct?
Other than the authentication failure on the user's device, is there any other apparent difference of any kind? Does everything else look the same up to that point?
Are both devices on the same network? Are both able successfully to ping the MobileTogether Server? Are both devices running the same version of the app? Which version of MobileTogether Server are you running? Which platform(s) are the devices running: the same, or different?
|
|
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 5/23/2016(UTC) Posts: 129 Location: Virginia Thanks: 20 times
|
Both have a mobile device on which the MobileTogether App is installed.
Both can enter the same details and credentials. I am able to connect but user cannot.
This is not at the same time. I am only attempting with my device after the user has failed and deleted the app from his device.
Other than the authentication failure there is no other difference than the type of device. They are all Androids using the Android version of the App from the Play Store.
I have an HTC and a Samsung Galaxy S3 which are on two different networks. I can access with either device.
One user in South Boston Virginia has a Samsumg Galaxy S4. He cannot connect
Another user in Chicago Illinois has a Samsung S7 Active. He cannot connect.
Both has the same problem. Password authentication is rejected.
All is the same except the network. Same version of the App, Same version of Mobile Together, MobileTogether Server 6.2, Android Platform.
Please advise on what else I should check or double check that could possibly create this problem.
Thanks,
|
|
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 5/23/2016(UTC) Posts: 129 Location: Virginia Thanks: 20 times
|
By the way, I changed the settings to login using anonymous and the user in Chicago was able to access the app.
I do not want this because I don't want users to be able to tell other users how to access the app without paying for it.
|
|
|
|
|
|
Rank: Administration
Groups: Registered, Administrators
Joined: 12/2/2015(UTC)
Posts: 11
|
Have you made certain the entered credentials (username and password) are exactly correct? You might try testing with a simple username and password combination (e.g., "a"/"b") which is unlikely to cause typographical errors. Note you can see the entered password by checking the Show Password option as described in the app documentation. I recommend you contact Altova Support directly, and supply one of the problematic credentials which definitely work for you so they can test. If possible, I would also include a screenshot (or photograph) of the device showing the credentials in use.
|
|
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 5/23/2016(UTC) Posts: 129 Location: Virginia Thanks: 20 times
|
Thanks, but I believe I have already solved the problem.
I unchecked "Allow MobileTogether Login via mt/login" and am using the "Use Customized Login and Index Page" option only. I assumed that this might eliminate the possibility of a problem with the cache on the client device. It appears to have worked. A new Client from North Carolina was able to use the credentials and log right in.
I am still waiting to hear back from the first two clients to see if it solved the problem for them. If it does not I'll contact Altova Technical Support.
|
|
|
|
|
|
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.
