View source | Discuss this page | Page history | Printable version   
Main Page
Upload file
What links here
Recent changes

PDF Books
Add page
Show collection (0 pages)
Collections help


Configuration Manual/Google Integration



This article describes the configuration required for integration with Google APIs.

Bulbgraph.png   This is Premium functionality. Learn more about the benefits of Openbravo's commercial editions
Warn-icon.png   This feature provides integration with OpenID2 which has been deprecated by Google, not allowing new registrations anymore. It can be replaced with OAuth2 integration by installing Google Sign In module.

Google Accounts

Starting from Openbravo 3.0MP2 you have the ability to log-in into an Openbravo instance using your Google Account.

You have the ability to log-on to an Openbravo instance using your Google Account. There are two ways to use the Google Accounts authentication service:

Bulbgraph.png   You need to be aware of the security implications of enabling the second option. This feature is offered for public instances like where the data is public, or for an instance behind a corporate firewall that is not public accessible. DO NOT ENABLE DEFAULT SETTINGS FOR NEW USERS IF YOUR INSTANCE IS PUBLIC ACCESSIBLE

Google Account association


Remove Association

Google Integration Preferences

New User Defaults


As explained in the section introduction Google_Accounts you can define some default role for your Client. This default role is the one that will be used to create a new user if the Google Account doesn't have any other user associated.


After configuring this default preferences, any user with a Google Account can log-in into the application. If no Openbravo user is associated a new one is created with the default previously defined.

Server Configuration

Apache Tomcat configuration

Bulbgraph.png   This configuration is only required if your made a Custom Installation

URIEncoding: This specifies the character encoding used to decode the URI bytes, after %xx decoding the URL. If not specified, ISO-8859-1 will be used.

The default encoding for parameters in Apache Tomcat is ISO-8859-1 and that leads to this error:

ERROR org.openid4java.consumer.ConsumerManager - Verification failed for: reason: null
ERROR - Error processing return of Google Auth Service:null

The solution is to set the encoding to UTF-8 in your connectors (depending on which one you're using)

Example (server.xml):

<Connector URIEncoding="UTF-8" connectionTimeout="20000" port="8080" protocol="HTTP/1.1" redirectPort="8443"/>

More information at openid4java forum post

Disabling Google integration

Professional Instances

You just need to create a new Preference with the property


Community Instances

If the integration with Google accounts is not required in your deployment you can disable this module.

To do it, as System Administrator, go to Application Dictionary || Module, select the module Integration with Google APIs and uncheck the field Enabled. Go to the login page and you can see that the sign in option with Google is not available.

Retrieved from ""

This page has been accessed 8,133 times. This page was last modified on 15 January 2015, at 08:47. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.