Microsoft Entra ID is a “universal platform to manage and secure identities”: https://www.microsoft.com/en-us/security/business/identity-access/microsoft-entra-id
Peerdom supports the most recommended single-sign-on methods: OpenID Connect and OAuth.
Check this 2 minute video, or continue reading below.
We will need your Azure Tenant ID to activate SSO authentication. This can be found via the Microsoft Entra Admin Center or the Azure Portal. In either case, the Tenant ID can be found in the Microsoft Entra ID > Overview
section. Note your Tenant ID as you’ll send it to us later.
In the App Registrations section, create a new application. Add a new Redirect URI:
Enter the newly registered Peerdom Sync App (from step 2) and create a new Client Secret in the Certificates & Secrets section. Choose the option: Never expire
. Note the Client Secret value for later.
Go to the API permissions tab on the Peerdom Sync App and add two permissions:
Directory.Read.All
User.Read.All
Approve the admin consent for both of these permissions on your organisation level by clicking on the button “Grant admin consent for ORGNAME”.
Peerdom synchronises with your Entra ID, meaning that your Peerdom directory will stay up to date with the current names and email addresses as defined in your Entra ID Directory. You will need to create a group with the users you’d like to synchronise. Create this group on Entra ID, add the members you’d like to appear on Peerdom, and write down the Group ID.
By default, Peerdom will accept all SSO log in attempts from your top-level domain. To restrict log in access to a particular group of users, you have two options:
We need the following:
Reach out to the person of contact, or send it to our support.