Hello!
We are developing a customized version of SugarCRM mobile and we would like to be able to force users to use this app, not the one Sugar provides us.
Is this possible?
thanks!!
Hello!
We are developing a customized version of SugarCRM mobile and we would like to be able to force users to use this app, not the one Sugar provides us.
Is this possible?
thanks!!
Perhaps you can update in app.json the attribute jsConfig.clientID to some value other than "sugar".
In the Sugar server side you can create a custom version of SugarOAuth2StorageMobile (custom/include/SugarOAuth2/SugarOAuth2StorageMobile) and override the method checkUserCredentials in order to evaluate if provided $client_id is "sugar", so you can refuse access.
Regards
Perhaps you can update in app.json the attribute jsConfig.clientID to some value other than "sugar".
In the Sugar server side you can create a custom version of SugarOAuth2StorageMobile (custom/include/SugarOAuth2/SugarOAuth2StorageMobile) and override the method checkUserCredentials in order to evaluate if provided $client_id is "sugar", so you can refuse access.
Regards
I also like this one! it seems I would have to touch less code... I'll also give it a try!
Thanks!
Hi André!
I've been trying to test your solution.
I've added one new record into oauth_consumer table. Here is where we place this client_id, right?
But I couldn't find any client_id or clientID option into app.json (according to documentation), in fact I've looked for it in the project with no luck.
Have you made this before? Do you know how to do it? any help would be really appreciated.
Thanks!
Thanks for the solution André!
I have got this to work for a customer who is using a custom mobile app (when using username/password) but we are running into issues when the users log in via Single Sign On as the clientId seems to be hardcoded somewhere to "sugar" in the SSO scenario.