Axero supports Google integration for single sign-on (SSO) out of the box. This page covers how to set up Google OAuth 2.0 credentials (the client ID and secret that let your site use Google sign-in), how to turn on Google integration, and what the Google login looks like.
Setting up Google SSO takes about 1-2 hours. Once you complete the guide, Google SSO will be active on your intranet. For help from the Axero team, submit a private case.
There are two ways to let people sign in to Axero with Google, and they are not interchangeable. Read this before you start.
https://my.intranet.com
https://myintranet.com/oauth2/google/callback
The Enable Google integration checkbox stays grayed out until both the API key and the Secret are filled in, so enter those two first.
When someone signs in with Google for the first time, Axero creates their intranet account from the information Google returns:
Axero picks the username from the person's first name, adds the last name if that username is taken, and adds a number after that. To have Axero assign a generated username instead, set the UseGenericSSOUsernames system property to true in Control Panel > System > System Properties.
true
On the login page, click the Sign in with Google button.
Enter your Google login information if Google asks for it.
If Auto approve members is unchecked in Control Panel > System > General Settings > Site Settings, you'll see a message that your account is pending approval.
The first time you sign in, you are asked to set your username.
You can customize the login page to show only the Google login option.
Before you do this: hiding the standard login fields leaves the Google button as the only way in. Anyone without a Google account linked to their profile, including you, will not be able to sign in from this page. Confirm that every account that needs access can sign in with Google, and keep a way to reach the site as an administrator, before you publish the change.
hide
Login button image
You can also change the login button image. Add the following code to CSS Overrides:
[id$='LoginUsingGoogle']:before { position: absolute; content: ''; background-image: url('https://developers.google.com/identity/images/btn_google_signin_light_normal_web.png'); width: 191px; height: 46px; pointer-events: none; z-index: 20000;}
Signing in with Google is not available in Mobile Apps. On a site with no SAML provider set up, people sign in to the app with their username or email and their Axero password. On a site that uses a SAML provider, including Google Workspace configured as one, the app signs people in through that provider instead.
To set an Axero password for the app, select your name in the header, then Password.
Error: redirect_uri_mismatch
Fix: Make sure the value in Authorized redirect URIs is your site address followed by /oauth2/google/callback, starting with https, and matches the address people use to reach your site.
Exception: "UserCreateStatus status: InvalidPassword" when someone new tries to sign in.
Fix: Axero creates a 13-character password for a new Google account, so the site's password length limits have to allow a value of that length.
If a validation pattern has been applied to the Password profile field, that pattern replaces both length settings, and the settings above will have no effect. In that case, the pattern itself has to accept a 13-character password.
Exception: "UserCreateStatus status: InvalidUserName" when someone new tries to sign in.
Fix:
This happens because Axero builds the username from the person's first name, which can be shorter than the site's minimum. If you would rather not loosen the username rules, set the UseGenericSSOUsernames system property to true instead. Axero then assigns a generated username to accounts created through single sign-on, and the person is prompted to choose their own on first sign-in.
is requesting access to a wiki that you have locked: https://my.axerosolutions.com/spaces/5/axero-documentation/wiki/view/22929/google-sso
Your session has expired. You are being logged out.