LogoLogo
3.6.9
3.6.9
  • Introduction
  • Getting started
    • Installation
      • Prerequisites
        • Server requirements
      • On-premises
        • Single-node
          • Directory structure
        • Multi-node
      • Azure Market Place
      • AWS Market Place
    • Tutorials
      • Amazon AWS CUR
      • Amazon AWS CUR (Athena)
      • Azure Stack
      • Azure EA
      • Azure CSP
      • Google Cloud
      • VMware vCloud
      • VMware vCenter
    • How-to guides
      • How to configure receiving a monthly billing report
      • How to automatically trigger a monthly billing report
      • How to update your license
      • How to store contract information with an Account in a report
      • How to automatically send workflow errors as webhooks to a monitoring system
    • Concepts
      • User interface
      • Services
    • Releases
      • Upgrading to version 3
      • Known issues
      • Announcements
      • Archive
  • Reports
    • Accounts
    • Services
    • Instances
    • Summary
    • Budget
  • Services
    • Manage
    • Rates
      • Tiered Services
        • Aggregation Levels and the Account Hierarchy
    • Adjustments
    • Subscriptions
  • ACCOUNTS
    • Budget management
  • Data pipelines
    • Extract
      • Configuration
      • Extractor templates
      • Script basics
      • Parslets
      • Subroutines
        • check_dateformat
        • check_dateargument
        • format_date
        • validate_response
      • Language
        • aws_sign_string
        • basename
        • buffer
        • csv
        • clear
        • decimal_to_ipv4
        • discard
        • encode
        • encrypt
        • environment
        • escape
        • exit_loop
        • foreach
        • generate_jwt
        • get_last_day_of
        • gosub
        • gunzip
        • hash
        • http
        • if
        • ipv4_to_decimal
        • json
        • loglevel
        • loop
        • lowercase
        • match
        • pause
        • print
        • return
        • save
        • set
        • subroutine
        • terminate
        • unzip
        • uppercase
        • uri
        • var
    • Transform
      • Configuration
      • Transformer templates
      • Transform Preview
      • Language
        • aggregate
        • append
        • calculate
        • capitalise
        • convert
        • copy
        • correlate
        • create
        • default
        • delete
        • dequote
        • environment
        • event_to_usage
        • export
        • finish
        • Functions
        • if
        • import
        • include
        • lowercase
        • normalise
        • option
        • rename
        • replace
        • round
        • services
        • set
        • sort
        • split
        • terminate
        • timecolumns
        • timerender
        • timestamp
        • update_service
        • uppercase
        • var
        • where
    • Datasets
    • Lookups
    • Metadata
    • Reports
    • Workflows
  • Administration
    • User management
      • Users
      • Groups
    • Notifications
      • Budget Notifications
      • Report notifications
      • Workflow notifications
    • Settings
      • Global Variables
      • White Labeling
  • Advanced
    • Integrate
      • GUI automation
        • Examples
      • API docs
      • Single sign-on
        • Claims-based identity provisioning: users, Account access and user groups
        • Azure-AD
        • Auth0
        • OKTA
        • OneLogin
        • ADFS
        • LDAP
    • Digging deeper
      • Authentication flows
      • Transformer datadate
      • Dataset lifecycle
      • Config.json
      • Databases
  • Security
    • Security
    • Authentication
      • Token
      • LDAP
      • SAML2
    • Password reset
    • Password policy
    • Announcements
  • Troubleshooting
    • Logs
  • Terms & Conditions
  • Privacy Policy
Powered by GitBook
On this page

Was this helpful?

Export as PDF
  1. Advanced
  2. Integrate
  3. Single sign-on

OKTA

Learn how to integrate Exivity with Okta

PreviousAuth0NextOneLogin

Last updated 3 years ago

Was this helpful?

In order to use Okta as an Identity Provider, we need to set up a new application. The following steps will guide you through the setup and configuration: 1. Select the Applications section from the menu on the left and click Applications. A dashboard will open where you have the option to create new applications. To do so, click Create App Integration:

2. Select the SAML2.0 type of integration and click Next.

3. Choose a relevant name for your app. You also have the option to add your logo. Click Next to go to the SAML configuration screen.

4. Next, you must fill in the General information for the SSO URL and the SP Entity ID.

In a separate browser tab, open Exivity, navigate to Administration > Settings > Single sing-on and copy the values from the Endpoints section to your Okta configuration with the following mapping:

The Single Logout option is not mandatory to configure, therefore your SSO Okta integration with Exivity will work accordingly without it.

5. Click Next, fill in the additional questions requested by Okta, and then finally, click Finish.

6. Now that you created your application, navigate to the Sing on tab and click the View Setup Instructions button in the yellow box.

7. The values from the following screen have to be inserted into the Exivity Single sign-on settings screen with the following mapping:

8. Click Update to save your configuration.

9. In order to have a completely functional configuration, we must add the Okta domain name to the CORS origins whitelist known by Exivity. Navigate to the System tab in the Administration > Settings menu and add your domain in the CORS origins field.

Your domain may look similar to: https://name.okta.com

Make sure to separate the CORS origins domains with a comma.

10. Click Update to apply your new settings.

11. Enable Single Sign-On in Exivity by navigating to Administration > Settings and then clicking on the System tab. Make sure the Single Sign-On option is set to an option including SAML2 Authentication:

12. Click Update to apply your change.

13. Log out of the current session and you will be redirected to the login page which may look like this:

14. And by clicking on the Login button, you'll be taken to the Okta login screen.

Creating an App in Okta
Selecting SAML2.0 for your Exivity integration
Customizing the Okta app
Filling in SSO URL and Entity ID
Mapping between Okta and Exivity
Setup instructions for SAML2 integrations with Exivity
SAML2 mapping between Okta and Exivity
Adding Okta to the CORS whitelist
Enable Single Sign-On
SSO login