You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 3, 2017. It is now read-only.
casLogin appears to be defective. I had to modify my local CAS server to allow callbacks to 'http' urls (which is fine) and with that change , once I login to uMobile as admin/admin, for some reason the JS code doesn't recognize the uid and always returns 'guest' even though CAS shows that I have successfully logged in and validated the ticket:
uMobile.js:
Looked at CredentialsView in umobile.js and the 'admin' username appears to correctly be saved into the model.
authentication.js;casLogin():
On the success callback, the 'credentials.attributes.username' returns admin. However, 'data.user' returns 'guest'?
So it looks like there's a mismatch between credentials model/view where the uid isn't saved into local storage, or something like that...
The text was updated successfully, but these errors were encountered:
Thanks for opening a ticket with uMobile app phonegap. 👍 🙇♂️
The uMobile app phonegap is no longer being actively maintained. ⛔
For alternatives we recommend the uMobile Android App and the uMobile iOS app. ✅
Thanks again for contributing to the uMobile app phonegap! ✨
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
casLogin appears to be defective. I had to modify my local CAS server to allow callbacks to 'http' urls (which is fine) and with that change , once I login to uMobile as admin/admin, for some reason the JS code doesn't recognize the uid and always returns 'guest' even though CAS shows that I have successfully logged in and validated the ticket:
uMobile.js:
authentication.js;casLogin():
So it looks like there's a mismatch between credentials model/view where the uid isn't saved into local storage, or something like that...
The text was updated successfully, but these errors were encountered: