If your users have Google accounts you can configure Infiniti or LibPaths to allow them to automatically authenticate via Google. Their Google account can be configured to match with either their username or their email address. Users who do not have their email address recorded in Concord in either of the username or email field, or users who do not have a Google account will be required to authenticate using their username and password.

Note: The following tasks should be implemented by an IT specialist who has competency with Google account management.  

Go to: 
Settings> System > Integration > Google Sign-In  
  1. Decide which Google account that the librarians, the IT department or the school in general will use to manage their Google Client-Server relationship - create one if necessary. This account should be accessible by at least one library manager but preferably not an individual's specific Google account, e.g., {schoolname}@google.com.au
  2. Decide whether you will match each user's email addresses with either:
    1. Their username in Infiniti or LibPaths (must be an email address) - this may require alignment of existing usernames to matching email addresses using a CSV file
    2. The email address stored in the user records. You can import user email addresses if you take this option
  3. Logon to Google using this account.
  4. Go to: https://console.developers.google.com whilst logged into Google as this Google account user.
  5. Create a New Project. Call it something relevant to your school and library, e.g., {schoolnameLibrary}Note: If Google is not creating a project correctly for you you may need to register billing information against this Google account in order for Google to perceive the account as a "real person". You will not need to enable any billable API for Infiniti or LibPaths, nor will Infiniti or LibPaths use any billable API for Google Sign-In.
  6. In Infiniti or LibPaths, click on Show Google Details on Integration configuration tab
  7. Copy URL (Ctrl/C) from Authorised JavaScript Origins.
  8. In Google developer console, select your created Project > Credentials > click Create credentials > click OAuth client ID Note: Google may prompt you to configure your application's "consent screen", i.e., the popup that the end-user will see at initial logon stage. You may populate this screen with whatever you see fit but the Infiniti core URL {schoolname.concordinfiniti.com} should be added to the Authorised domain box and screen saved. Leave blank any field you are uncertain about.
  9. In Google developer console, select Application type 'Web application' for OAuth client ID with a relevant Name.
  10. Paste (Ctrl/V) URL from Infiniti into Authorised JavaScript Origins and click Create button
  11. Copy the Client ID and Client Secret across to the respective fields on the Integration configuration tab.
  12. Choose to match an end-user's Google account email address against either their username or email address field, depending on how your library is managing users. NB: If the user's Google email address does not match the field you have chosen, then the user will be required to log on using their username and password.
  13. Log out of your Google account for the Google Developers Console and in general for Google services.
  14. Decide on a Google account for testing. This may be your personal Google account or any other Google account. NB: Ensure that you have a Infiniti or LibPaths user with this Google account's email address registered in the applicable field in Infiniti or LibPaths.
  15. Press the "Test Sign-In" button on the Integration configuration tab. If everything has been configured correctly you should be prompted to establish a relationship between Google and Infiniti or LibPaths. Once accepted and matched to an enabled Infiniti or LibPaths user, a successful test message should appear.
  16. Once you are satisfied with your testing you can clickand enable the Google Sign-In feature for your library. Note: You are delegating trust to Google for the purposes of authenticating users. Any enabled user who has a Google-managed email address registered for their Infiniti or LibPaths account (in the chosen match field of username or email address) can logon into Infiniti or LibPaths automatically via the "Sign in with Google" button.