How to install and configure J-SugarCRM Authentication Plugin

About two years ago, I developed a plugin that adds an additional driver of a Joomla user authentication. The plugin allows access to the Joomla portal for users of SugarCRM. The installation and configuration of this plugin is very simple, but I have received several comments with requests for help on the process of installation and configuration, this explains the reason for this short post.

The current version of the plugin is compatible with Joomla version 1.7 and 2.5 and supports SugarCRM versions: 6.1, 6.2 CE/PRO/ENT. In one of the comments received, someone asked me if it was supported version 6.5.8 of SugarCRM, this evening I had the opportunity to do a test with a positive result, but I was able to test only the edition Community. But I think it should also work with other editions, the API should be the same.

Requirements before proceeding with the installation and configuration are:

  • Connection to the Internet;
  • An instance of Joomla 1.7 or 2.5;
  • An instance of SugarCRM supported by the J-SugarCRM Authentication Plugin;
  • A SugarCRM SOAP service endpoint (eg;
  • Instances of the CMS and CRM should be visible at the network layer (http protocol).

Installation and Configuration

To install the plug-in is required to access the control panel of Jommla by an admin user. In Figure 1 and 2 show the installation of the plugin.

I decided to do the installation by entering the address (http) of the plugin, which in this case is:

You can still follow the other installation options.

Figure 1 - Installation of the Plugin

Figure 1 – Installation of the Plugin

Figure 2 - Installation Successful of the Plugin

Figure 2 – Installation Successful of the Plugin

In Figure 3 and 4 there is shown the configuration of the plugin. The most important parameter is the address of SugarCRM SOAP service, in particular the WSDL document. If you want to test the plugin, you can use the instance of SugarCRM CE (version 6.5.4) deployed on the cloud of Red Hat at:

  • Application URL
  • Web Services SOAP URL
Figure 3 - List of the installed plugin

Figure 3 – List of the installed plugin

Figure 4 - Configuration of the Plugin

Figure 4 – Configuration of the Plugin

After you save the configuration, you can perform an authentication test. The configuration shown in Figure 4 is the standard one, for an edition of SugarCRM Community.

Test access to Joomla

At this point you can test authentication on Joomla, using a user defined on SugarCRM. In case you have decided to use my SugarCRM instance, you could use the following credentials to run the test:

  • Username: will
  • Password: will

In Figure 5 and 6 show the login form and the next page after authentication.

Figure 5 - The Joomla login form

Figure 5 – The Joomla login form

Figure 6 - User Profile page after authentication

Figure 6 – User Profile page after authentication


In this short post I hope I was good at explaining the process of installing and configuring the plugin integration between Joomla and SugarCRM. All your comments are well appreciated.

Antonio Musarra

I began my journey into the world of computing from an Olivetti M24 PC ( bought by my father for his work. Day after day, quickly taking control until … Now doing business consulting for projects in the enterprise application development using web-oriented technologies such as J2EE, Web Services, ESB, TIBCO, PHP.

You may also like...

Cos'è il progetto CIE/CNS Apache Docker - Developers Italia

In questo video introdurrò il progetto CIE/CNS Apache Docker di Developers Italia ( nato circa due anni fa.

L'obiettivo di questo progetto è quello di fornire un template pronto all'uso che realizza un sistema di autenticazione tramite la Smart Card TS-CNS (o CNS) e la CIE (Carta d'Identità Elettronica) basato su Apache HTTP. Ognuno può poi modificare o specializzare questo progetto sulla base delle proprie esigenze Si tratta di un progetto docker per la creazione di un container che implementa un sistema di mutua autenticazione o autenticazione bilaterale SSL/TLS.

Questo meccanismo di autenticazione richiede anche il certificato digitale da parte del client, certificato che in questo caso risiede all'interno della TS-CNS o della CIE. La particolarità del sistema implementato (attraverso questo container) è quella di consentire l'autenticazione tramite:

  • La TS-CNS (Tessera Sanitaria - Carta Nazionale Servizi), rilasciata dalla regione di appartenenza;
  • La CIE (Carta d'Identità Elettronica), rilasciata dal comune di residenza.

Nella versione 2.0.0 il progetto è stato aggiornato per essere uniforme alle linee guida di Bootstrap Italia. A seguire alcune risorse che possono essere utili.

  • Cos’è il progetto CIE/CNS Apache Docker (
  • CIE Carta d'Identità Elettronica (
  • Carta Nazionale dei Servizi (
  • Raspberry Pi – Un esempio di applicazione della TS-CNS (
  • Pubblicare il servizio CIE/CNS Apache Docker su Azure Cloud (
  • Come accedere al portale VETINFO tramite TS-CNS e Mac OS (