LogoLogo
  • What is LIBSAFE ADVANCED
  • LIBSAFE Advanced Benefits
  • CONCEPTS
    • Overview
    • Organize your content
    • Active escrow data protection
    • Platform architecture
    • OAIS and ISO 16363
      • Understanding OAIS and ISO 16363
      • LIBSAFE Advanced support for OAIS Conformance
      • Planning for preservation
      • ISO 16363 certification guide
  • GET STARTED
    • Create a data container
    • Upload content
    • Download content
    • Introduction to metadata
    • Search
    • File versioning and recovery
    • Work with data containers
    • Functions
    • Storage mode transitions
    • Jupyter Notebooks
    • OpenAccess Integration
      • Transfer Connector
      • LIBSAFE Configuration
      • OpenAccess Configuration
      • Multilanguage
      • Supported Formats
      • Changelog
  • CONFIGURATION
    • Archive organization
    • Container templates
    • Configure metadata
    • Users and Permissions
  • REPORTS
    • Introduction
    • Data Analytics Reports
    • Container Tab Reports
  • DEVELOPER'S GUIDE
    • Functions
    • Using the API
    • Functions gallery
  • COOKBOOK
    • AWS CLI with LIBSAFE Advanced
    • Using S3 Browser
    • Using FileZilla Pro
    • Getting your S3 bucket name
    • Getting your S3 storage credentials
    • Advanced API File Search
    • Tips for faster uploads
    • Configuring Azure SAML-based authentication
    • Configuring Okta authentication
    • Create a manifest before transferring files
  • File Browser
    • Supported formats for preview
    • Known issues and limitations
  • Changelog and Release Notes
Powered by GitBook
On this page
  1. COOKBOOK

Configuring Okta authentication

PreviousConfiguring Azure SAML-based authenticationNextCreate a manifest before transferring files

Last updated 2 years ago

In order to configure Okta with our services, your institution must create a new SAML 2.0 application with the following details:

  • Single sign-on URL:

  • Audience URI (SP Entity ID):

  • Default RelayState: [leave blank]

  • Name ID format: Persistent

  • Application username: Okta username or Email (the value MUST be unique for each user)

After this is done, please forward us the IDP Metadata to complete the integration. To obtain the metadata, follow these steps:

https://access.libnova.com/Shibboleth.sso/SAML2/POST
https://access.libnova.com/shibboleth
Step 1
Step 2
Step 3 - fill in with the above information
Step 4
Step 5
Step 6 - Copy the IDP metadata to a text file and save it with a .xml extension.