Tipalti Help Center home page
  • Get started
    • Onboarding tools
    • Video tutorials
    • Live training
  • User guide
    • Log into the Tipalti Hub
    • Administration
      • Administrative operations
      • User roles
    • Multiple entities
    • Funding
      • View funds required
      • Fund Tipalti accounts
      • Multi-FX
        • Currency cutoffs and validations
    • Payees overview
      • Search payee information
      • Manage payee status and settings
      • iFrame/ Supplier Hub
      • Manage Supplier Hub payees
      • Documents review
    • Taxation
      • US tax forms
      • Tax form expiration
      • Tax withholding
        • Withholding rates
        • Income types
        • Tax form and entity types
      • Certificate of No US Activities
      • Additional documents
      • Non-US tax collection
      • Tax form statuses
    • Procurement
      • System overview
      • Create and track purchase requests
      • Approve purchase requests
      • Mark goods and services as received
      • Vendor registration
      • Send PO PDF
      • Back office
        • Set reminders
        • Run parallel PR/ vendor approval
        • Emails
        • PO PDF customization
        • Upload budget
        • Customize Procurement forms
        • Contract repository
      • Workflow integrations
    • PO Matching
      • Matching process
      • Handle matching exceptions
      • Bill routing
      • Matching policies
      • Bill coding
      • Bill approval for PO-backed bills
        • Approvable bills
        • Non-approvable bills
        • PO updates
      • Prepayments (NetSuite 2.0)
      • Track and match a dropship invoice
        • Set payees up as dropship vendors
        • Upload and match a dropship invoice
    • Bills
      • Bill flows
      • Usability
      • Add invoices
      • Manage bills
      • Add comments and files to bills
      • Bill approvers
        • Invoice processing approvals
          • Email security
      • Tax collection in Bills
      • Bill statuses
    • Tipalti Expenses
      • Get started
      • Create and submit expenses
      • Manage and approve expenses
      • Reimburse expenses
      • Connect your corporate cards
    • Tipalti Cards
      • Funds flow
      • Manage cards
      • Card transactions overview
      • Process transactions
      • ERP sync
      • Credit card statement report
    • Submitting payments
    • Payment information
      • Payment statuses
      • Payment methods coverage
      • Payment methods coverage: US and ROW
      • Payment methods coverage: UK and EU
      • Payment error codes
    • Generate reports
      • Smart report builder
      • Payment reports
      • Bill reports
      • Payee reports
      • Tax reports
      • User reports
    • Security practices
      • Email security
      • Business continuity practices
      • Two-factor authentication
    • Detect
  • Integrations
    • 3rd Party Apps
      • Partner Platforms
      • SSO
    • ERPs
      • Sage Intacct
      • NetSuite 2.0
      • Microsoft Business Central
      • QuickBooks
      • Xero
      • Tipalti Connect
      • Acumatica
      • SAP B1
        • Setup
        • SAP B1 PO Matching
    • File Integration
      • Configure auto-sync settings
      • Import files
      • Export files
  • FAQs
    • General FAQs
    • User guide FAQs
      • Bill FAQs
      • Card FAQs
      • PO Matching FAQs
      • Payment FAQs
      • Detect FAQs
      • Taxation FAQs
      • Administration FAQs
      • Expenses FAQs
    • ERP FAQs
  • Release notes
  • Dev docs
Sign in
  • Get started  
    • Onboarding tools  
    • Video tutorials  
    • Live training  
  • User guide  
    • Log into the Tipalti Hub
    • Administration  
      • Administrative operations
      • User roles
    • Multiple entities
    • Funding  
      • View funds required
      • Fund Tipalti accounts
      • Multi-FX  
        • Currency cutoffs and validations
    • Payees overview  
      • Search payee information
      • Manage payee status and settings
      • iFrame/ Supplier Hub
      • Manage Supplier Hub payees
      • Documents review
    • Taxation  
      • US tax forms
      • Tax form expiration
      • Tax withholding  
        • Withholding rates
        • Income types
        • Tax form and entity types
      • Certificate of No US Activities
      • Additional documents
      • Non-US tax collection
      • Tax form statuses
    • Procurement  
      • System overview
      • Create and track purchase requests
      • Approve purchase requests
      • Mark goods and services as received
      • Vendor registration
      • Send PO PDF
      • Back office  
        • Set reminders
        • Run parallel PR/ vendor approval
        • Emails
        • PO PDF customization
        • Upload budget
        • Customize Procurement forms
        • Contract repository
      • Workflow integrations
    • PO Matching  
      • Matching process
      • Handle matching exceptions
      • Bill routing
      • Matching policies
      • Bill coding
      • Bill approval for PO-backed bills  
        • Approvable bills
        • Non-approvable bills
        • PO updates
      • Prepayments (NetSuite 2.0)
      • Track and match a dropship invoice  
        • Set payees up as dropship vendors
        • Upload and match a dropship invoice
    • Bills  
      • Bill flows
      • Usability
      • Add invoices
      • Manage bills
      • Add comments and files to bills
      • Bill approvers  
        • Invoice processing approvals  
          • Email security
      • Tax collection in Bills
      • Bill statuses
    • Tipalti Expenses  
      • Get started
      • Create and submit expenses
      • Manage and approve expenses
      • Reimburse expenses
      • Connect your corporate cards
    • Tipalti Cards  
      • Funds flow
      • Manage cards
      • Card transactions overview
      • Process transactions
      • ERP sync
      • Credit card statement report
    • Submitting payments
    • Payment information  
      • Payment statuses
      • Payment methods coverage
      • Payment methods coverage: US and ROW
      • Payment methods coverage: UK and EU
      • Payment error codes
    • Generate reports  
      • Smart report builder
      • Payment reports
      • Bill reports
      • Payee reports
      • Tax reports
      • User reports
    • Security practices  
      • Email security
      • Business continuity practices
      • Two-factor authentication
    • Detect  
      • Usability
      • Manage Payee risk
  • Integrations  
    • 3rd Party Apps  
      • Partner Platforms
      • SSO
    • ERPs  
      • Sage Intacct
      • NetSuite 2.0
      • Microsoft Business Central
      • QuickBooks
      • Xero
      • Tipalti Connect
      • Acumatica
      • SAP B1  
        • Setup
        • SAP B1 PO Matching
    • File Integration  
      • Configure auto-sync settings
      • Import files
      • Export files
  • FAQs  
    • General FAQs
    • User guide FAQs  
      • Bill FAQs
      • Card FAQs
      • PO Matching FAQs
      • Payment FAQs
      • Detect FAQs
      • Taxation FAQs
      • Administration FAQs
      • Expenses FAQs
    • ERP FAQs
  • Release notes
  • Dev docs
  1. Tipalti
  2. Integrations
  3. 3rd Party Apps
  4. SSO

Articles in this section

  • SSO
  • Azure
  • Google Workspace
  • Okta
  • OneLogin
    Skip To Main Content
    Account
    Settings
    Logout
    • placeholder
    Account
    Settings
    Logout
    Filter:
    Submit Search

        Okta setup

        Follow these steps to set up Okta as an SSO provider for the Tipalti app.

        ClosedStep 1. Create a new app integration
        1. In Okta, go to Applications > Applications.
        2. Okta Application

        3. On the "Applications" screen, click "Create App Integration".
        4. Add application button

        5. On the "Create a new app integration" screen:
          1. For the "Sign-in method" field, select "OIDC - OpenID Connect".
          2. For the "Application type" field, select "Web Appplication"
          3. Click "Next" to open the "New Web App Integration" screen.
          4. Create a new app integration page in Okta

        ClosedStep 2. Identify the Tipalti app to Okta's OpenID servers

        On the "New Web App Integration" screen, complete the following fields:

        1. In the "App integration name" field, type:
          • "Tipalti-Sandbox", if you are setting up the Sandbox app.
          • "Tipalti-Production", if you are setting up the Production app.
        2. In the "Logo" field, upload Tipalti's logo.
        3. In the "Sign-in redirect URIs" field, click "Add URI", and add 2 URIs for each environment. Copy and paste the following URIs.
          • 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
        4. In the "Assignments" section, you can assign the app to users/ groups and configure their roles:

          1. For the "Controlled access" field, select "Limit access to selected groups".

          2. For the "Selected group(s)" field, enter the group in your organization to whom you want to assign the app integration.

        5. Click "Save".
        ClosedStep 3. Send your "Client ID", "Client secret" and "Well-known authorization URL" to Tipalti

        You need to copy the credential values from Okta, and paste into a secured text password-sharing application (e.g., 1Password, Value), as you need to provide Tipalti with these values for each application (Sandbox and Production) to complete the setup process.

        1. You can build the "Well-known authorization URL" as follows: https://YOUR_OKTA_DOMAIN/.well-known/openid-configuration where "YOUR_OKTA_DOMAIN" is the domain of the Okta application's Issuer.
        2. For example, if the Issuer was https://your-company.okta.com, then the well-known URL would be https://your-company.okta.com/.well-known/openid-configuration

        3.  On the "Tipalti-Sandbox" screen, click "General":
          1. In the "Client Credentials" section:
            1. Copy the value in the "Client ID" field and paste it into the secured text password-sharing application.
            2. In the "Client secret" field, click the eye icon, copy the value and paste it into the secured text password-sharing application.
            3. Clien credentials section

              If required, you can generate a new "Client secret". In the "Client Credentials" section, click "Edit" and then the "Generate New Client Secret" button.

          1. In the "Allowed Grant Types" section, select "Implicit". 
          2. In the "Login" section, for the "Login initiated by" field, click the dropdown and select "App Only". 
          3. Login initiated by field

          4. Click "Save.
          5. Send the document containing your "Client ID", "Client secret" and "Well-known authorization URL" to Tipalti to finish the SSO configuration process.
          6. Once Tipalti confirms that your credentials have been received, destroy the document.

        If you want to support launching your application from the Okta dashboard, on the "Tipalti-Sandbox" screen, click "General" and in the "Login" section:

        1. For the "Sign-in redirect URIs" field, enter one or more URI values where Okta sends the OAuth responses.
        2. (Optional) For the "Sign-out redirect URIs" field, add a URI where Okta redirects the browser after it receives the sign-out request from the relying-party and terminates the end user's session.
        3. For the "Login initiated by" field, click the dropdown and select "Either Okta or App" to give your integration an tile.
        4. When you select the "Either or App" option, an "App Embed Link" section appears at the bottom of the page with the URL that can be used to sign in to the OIDC client from outside .

        5. For the "Application visibility" field, select "Display application icon to users".
        6. For the "Login flow" field, for OIN app integrations, select "Redirect to app to initiate login (OIDC Compliant)".
        7. For the "Initiate login URI" field, enter or change the URI used to initiate the sign-in request.
        8. Click "Save".
        9. Login section

        • ZD.4.log-1212665864.zip
          20 KB Download
        Was this article helpful?

        We’d love the opportunity to improve. Submit your feedback.

        We’re glad you enjoyed the article!

        Have more questions? Submit a request
        Return to top
        Privacy Policy | Terms of Use | Payer/Sender Rights | Customer Assistance Policy
        LinkedIn Instagram Facebook Twitter YouTube
        Contact support