Axero supports Facebook integration for single sign-on (SSO) out of the box. This page covers how to configure a Facebook app, how to turn on Facebook Login in Axero, and what the Facebook login looks like.
Most of the work happens on Facebook's side. How long it takes depends on how quickly Facebook completes business verification and app review for your app, which is outside Axero's control. Once Facebook approves your app and you enter its credentials in Axero, Facebook Login will be active on your intranet. For help from the Axero team, submit a private case.
Facebook changes this part of its site from time to time, so a button may sit somewhere slightly different from what is described here. The settings themselves are stable.
myintranet.com
https://myintranet.com
Axero matches a person's Facebook account to their Axero account by email address, so your Facebook app needs permission to read it. Facebook treats the two pieces of information Axero asks for differently.
This is the step most often missed, and skipping it looks like a working setup. Facebook login works for the administrator who built the app, but for nobody else at your organization.
Those two permissions are the only ones Axero requests. It does not ask for friend lists, posts, or anything else a person shares on Facebook, and it cannot post on their behalf. People see exactly this on the Facebook confirmation screen when they sign in.
You can return to your app's settings at any time at https://developers.facebook.com/apps.
When someone joins using their Facebook account, Axero fills in their name and email address and uses their Facebook profile photo as their Axero profile picture. Everything else on their profile starts empty, which is why they are asked to complete any required fields on the way in. When they return, they can sign in with Facebook again.
People can uncheck the email address on the Facebook confirmation screen before they continue. When Facebook supplies no email address, Axero falls back to a placeholder in the form username_no_email@temp.com. An account with a placeholder address cannot be matched to an existing member. It also will not receive email from your intranet until someone corrects the address, so check new members for those addresses.
username_no_email@temp.com
Note: an existing member is linked to their Facebook account only if the email address on their Axero account is the same as the email address on their Facebook account. If the two differ and they sign in with Facebook, Axero adds them as a new member instead of linking. Once the two accounts have been linked the first time, the link holds even if the member's email address changes later.
If your intranet requires an administrator to approve new members, the account is created but stays inactive until someone approves it.
Only the people who built the Facebook app can sign in successfully.
Until Facebook approves advanced access for the email permission, it will not release email addresses to anyone who does not have a role on your Facebook app. Everyone else either cannot get past the Facebook screen or arrives as a brand-new account that is not matched to their existing intranet account. Complete Request access to email addresses above.
Exception: "UserCreateStatus status: InvalidUserName" when someone new tries to sign in.
Axero builds the new username from the person's Facebook first name, and that name has to fit your intranet's username rules. Two things can break it.
If the name is too short or too long:
If the name contains accented or non-Latin characters, no length setting will help. Usernames accept only unaccented letters, numbers, and four punctuation characters: hyphen, underscore, period, and comma. That is the default rule, and an administrator can replace it with a different pattern. Instead, have Axero generate a neutral username:
true
New members then receive a generated username such as user004821, which they can change on the Choose your username screen. Make sure your minimum and maximum username lengths allow 10 characters.
user004821
Exception: "UserCreateStatus status: InvalidPassword" when someone new tries to sign in.
People signing in with Facebook never type an Axero password, so Axero generates one for them. It is 13 characters long, and it has to fit your intranet's password rules.
These two settings apply to everyone on your intranet, not only to people signing in with Facebook, so weigh the change against your own password policy before you make it.
Exception: "UserCreateStatus status: EmailDomainNotAllowed" when someone new tries to sign in.
Your intranet restricts which email domains may register, and the address on the person's Facebook account is not on the list.
Alternatively, have the person change the email address on their Facebook account to one that is already allowed.
is requesting access to a wiki that you have locked: https://my.axerosolutions.com/spaces/5/axero-documentation/wiki/view/22927/facebook-sso
Your session has expired. You are being logged out.