Azure (Entra) setup
Follow these steps to set up Azure as an SSO provider for the Tipalti app.
Set up OIDC
Step 1. Register a new application
- Log in to your Azure account.
Use the same email you use to log into Tipalti - Under Azure services, click Microsoft Entra ID.
The company details display.
Step 2. Identify the Tipalti app to Microsoft Azure servers
Before you begin, have a secured text password-sharing application (for example, 1Password) ready to paste your app registration details in to share with Tipalti.
- Click App registrations in the left menu. Then, click + New registration in the top tab menu.
The Register an application page displays. - Complete the form:
- In the Name field, enter the name of the application.
- In the Supported account types field, select Accounts in this organizational directory only (tipalti.com only - Single tenant).
- Scroll down to the Redirect URI section.
- From the Select a platform dropdown, select Web.
- Copy and paste the following URLs for the Tipalti app.
- For Sandbox:
- https://console2.sandbox.tipalti.com/api/v0/account/authorizesso
- https://sso.sandbox.tipalti.com/api/authorization/v1/authorizesso
- For Production:
- https://hub.tipalti.com/api/v0/account/authorizesso
- https://sso.tipalti.com/api/authorization/v1/authorizesso
- For Sandbox:
- Click Register.
- Click Authentications in the left menu:
- In the Web section, click Add URl.
- Copy and paste a second URl (for the selected environment).
- For Sandbox:
- https://console2.sandbox.tipalti.com/api/v0/account/authorizesso
- https://sso.sandbox.tipalti.com/api/authorization/v1/authorizesso
- For Production:
- https://hub.tipalti.com/api/v0/account/authorizesso
- https://sso.tipalti.com/api/authorization/v1/authorizesso
- For Sandbox:
- Click Add URI.
- Click Save.
- Click Certificates & secrets in the left menu.
- In Client secrets, click + New client secret.
The Add a client secret right panel displays. - Complete the fields:
- In the Description field, enter a description for this client secret.
- Select the expiration period from the Expires dropdown based on your company policy. We recommend 365 days (12 months).
- Click Add.
The new client secret displays. -
Immediately, in the Value column, click the copy icon.
Once you leave the page, the value is no longer visible. - Paste and save the value to a secured text password-sharing application of your choice.
Step 3. Send your OIDC SSO credentials to Tipalti
To set up OneLogin as your SSO provider for Tipalti, you'll need to enter your OpenID Connect metadata document endpoint, Application (client ID), and Client secret key.
To complete the setup process, you need to provide Tipalti with the application registration details you generated in Azure using your secured text password-sharing application.
To get your Application (client ID) and OpenID Connect metadata document endpoint:
- In Azure, click App registrations.
- In either the All applications or Owned applications tab, go to your application listing.
-
In the Application (client) ID field, copy the ID and paste it into your secured text password-sharing application.
- Click Endpoints in the top menu..
- In the Endpoint right-pane, click the copy icon in the OpenID Connect metadata document field.
- Paste it into the secured text password-sharing application.
- Send the document to Tipalti through the secured text password-sharing application. Check the document contains the app:
- Application (client) ID
- Value
-
OpenID Connect metadata document endpoint
Tipalti sends you a confirmation email when they receive these details. The SSO configuration is now complete.
- Destroy the document as soon as you receive this confirmation.
Set up SAML
Step 1. Add the SAML app
- In the Azure Portal, go to Microsoft Entra ID.
- On the side panel, go to Enterprise applications.
- Click New application, then select Create your own application.
- Give the application a name and click Save.
You will now be redirected to the enterprise application page.
At this point, you may need to configure the user whitelist for this application.
Step 2. Configure the app
- On the side bar, go to "Manage → Single sign-on".
- Select SAML as the sign-in method.
You should now see a SAML configuration page. - Click "edit" on the basic SAML configuration box.
- Click both the add identifier and add reply URL links.
You now need to decide on an application identifier for this SAML application. We recommend tipalti.
This application identifier (or Entity ID) will be used for both the audience and issuer fields in IDS.
Step 3. Set up access control
- Under Entity ID, enter your chosen application identifier.
- Under reply URL, enter the appropriate callback URL.
- The rest of the fields are not required. Click Save.
The basic SAML configuration box should now be updated with the values you put in. - Copy and keep the value in the App Federation Metadata Url box. This is the metadata URL for configuring IDS.
After following these steps, you should have:
- Your configured Entity ID → audience + issuer
- The App Federation Metadata URL → metadata URL
You can now call the IDS API to configure SAML for this payer. Example:
{
"payerId": 1234,
"ssoMandatory": false,
"samlConfiguration": {
"audience": "tipalti",
"metadataUrl": "https://login.microsoftonline.com/6d9ed0f0-d90e-4251-9e94-078ded31a127/federationmetadata/2007-06/federationmetadata.xml?appid=5836eeb0-51a2-44e0-9864-421614edd0cd",
"issuer": "tipalti"
}
}