SOAP Authetication failing using c# after upgrade to 7.7? any suggestions? I get "Invalid Login" error.
Any help is really appreciated.
Hello Rama Reddy,
For Sugar 7.7, SOAP API,
Check this document from support site:
I think you should try to move towards REST API now.
We have also seen this issue (with integrations) with 7.7 and were advised that SugarCRM does not officially support SOAP API from Sugar 7.x
This worked fine in Sugar 7.6 however, what's changed between 7.6 and 7.7? Tests at our end reveal a successful login through SOAP calls on a local machine on both versions...
It also doesn't help there are no references to this change in the release notes, so it was impossible to foresee this when evaluating a customer's upgrade potential.
Just a bad situation from everyone's perspective
Hi Rama and David,
Please file bugs with support for problems you encounter with SOAP API. Please share the exact HTTP request that you are making that is failing when you report this issue as well as the response from the Sugar server.
While we have introduced a new API framework in the 7.x releases, that does not mean we have killed off the SOAP API by any means.
We contacted support many times and they are helpless. Finally we are planning to reverse the upgrade till we develop/convert code to new API or move to another platform like sales force. Users and Management will be meeting soon to take decision on this.
All the programs that are linked with the API fell apart and it is due for quarterly reports and meeting and we cannot run any reports that require SugarCRM data. It is frustrating moments for everyone here at my work place.
If you are running into this problem, please try passing your MD5 hash using lower case letters. It looks like a regression was introduced in Sugar 7.7 release. It also would explain why these SOAP login issues had been hard for Sugar Support to recreate.
Retrieving data ...