To setup Google Sign-in for Asset Bank, you will need to create a google application and obtain a client ID and secret key. This is needed to identify your Asset Bank and to ask for login permissions from users as a defined application.
To create the needed keys visit the Google Developer Console while you are logged into your Google account and follow these steps.
- Click on Create Project in the Manage resources screen
- Enter a Project name. You can optionally enter a Project ID or keep the auto-generated one
- Click on create, and wait for the project creation activities to finish. You will be redirected to the Project Dashboard page for the project. If you are not redirected automatically, then you may have a link in the notifications bell icon in the top right, or access it via the dropdown in the header, in the top left.
- In the Getting Started section, select 'Enable APIs and get credentials like keys'. You can also access this via the 'burger' menu icon in the top left > API Manager > Dashboard
- Navigate to 'OAuth consent screen', choose the User Type and click the 'Create' button
- Enter a Application Name in the appropriate field. This can be "[Your brand] Asset Bank" for example
- Choose an email address from the drop-down for the 'Support email' field
- Add your Asset Bank's URL to 'Authorised domains' field, then click on Save
- On the left hand side menu click on 'Credentials'
- Click on 'Create Credentials' and select 'OAuth client ID'
- Choose "Web application" for Application type
- Enter your Asset Bank's URL in the Authorised Javascript origins field
- Leave the content of the Authorised Redirect URIs empty as it is not used
- Click on 'Create'. The Project Dashboard page should now have some additional information on the right hand side
- You will need Client ID and Client Secret when configuring Asset Bank, so make sure you have a reference to these values
- Click on Library in the API Manager
- Find 'Google People API'
- Click 'Enable'
As a way of checking the configuration; in the API Manager > Credentials screen, you can click on the project that you have just created and use the button to 'Download JSON'. The JSON file should look like the example below:
{
"web": {
"client_id": "RANDOM_STRING_OF_CHARACTERS.apps.googleusercontent.com",
"project_id": "PROJECT_NAME",
"auth_uri": "https://accounts.google.com/o/oauth2/auth",
"token_uri": "https://accounts.google.com/o/oauth2/token",
"auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs",
"client_secret": "RANDOM_STRING_OF_CHARACTERS",
"javascript_origins": ["http://your.assetbank.domain", "https://your.assetbank.domain"]
}
}
Now that the Application has been created in the developer console, Asset Bank will need to be configured to use it for Google+ Login. If you are hosted with us, please get in touch, sending us the aforementioned JSON file, at this point.
If you host AssetBank on your own server infrastructure, you can do this by following these steps:
- In your Asset Bank webapp folder, navigate to the folder classes and create a copy of the file GooglePlusSSOSettings-standard.properties called GooglePlusSSOSettings.properties
- Edit the file and amend add the rows for client-id and client-secret similar to this snippet:
client-id=[Client ID created in the previous action] client-secret=[Client Secret created in the previous action]
- You can optionally set an application-name
- Save the changes
- Edit the file ApplicationSettings.properties and search for the entry sso-enabled and make sure it's set to true
- In the same file search for the entry sso-plugin-class and set the value GooglePlusSSOPlugin and save the file
- Restart Asset Bank

If the configuration was successful you should now see a Google+ Sign in button in the login screen. Depending on your configuration, users will be able to click on it for logging in. Visit Options for Single Sign On for more information.
Comments
0 comments
Please sign in to leave a comment.