Table of Contents

Search

  1. Preface
  2. Starting Data Archive
  3. System Configuration
  4. Database Users and Privileges
  5. Source Connections
  6. Target Connections
  7. Archive Store Configuration
  8. Datatype Mapping
  9. Database Optimization
  10. SAP Application Retirement
  11. z/OS Source Data Retirement
  12. Seamless Data Access
  13. Data Discovery Portal
  14. Security
  15. SSL Communication with Data Vault
  16. LDAP User Authentication
  17. Auditing
  18. Running Jobs from External Applications
  19. Salesforce Archiving Administrator Tasks
  20. Upgrading Oracle History Data
  21. Upgrading PeopleSoft History Data
  22. Data Archive Maintenance
  23. Appendix A: Datetime and Numeric Formatting
  24. Appendix B: Data Archive Connectivity

Administrator Guide

Administrator Guide

Single Sign-On Properties

Single Sign-On Properties

To enable single sign-on support through an identity provider that uses the SAML standard, configure the single sign-on properties.
The
conf.properties
file includes the following single sign-on properties:
informia.sso.enable
Enables single sign-on. Enter Y to enable single sign-on. Enter N to disable it.
Default is N.
informia.idp.metedata.file
Path to the identity provider's metadata file.
Example: informia.idp.metedata.file = c:\\metadata
informia.key.path
Path to the KeyStore that you created during single sign-on configuration.
Example: c:\\generatedKeys
informia.key.alias.name
Alias name for the KeyStore that you created during single sign-on configuration.
Example: informia.key.alias.name = testkey01
informia.key.password
Password for the KeyStore. Before you update the property, this password must be encrypted using the encrypt password utility provided in Data Archive.
Run the command below to encrypt the password from the ILM directory:
-"encryptPassword.bat testkey01" for Microsoft Windows
-"encryptPassword.sh testkey01" for Unix
Example: informia.key.password = D1YgPl914QpCtSgoHWbsCg==
informia.idp.home.url
The identity provider's home URL. This parameter is not required for all identity providers (Okta, Onelogin).

0 COMMENTS

We’d like to hear from you!