Redwood Documentation

Product Documentation

 

›Configuration

RunMyJobsRunMyJobs On-Premises Installation

Preparing Installation

  • Preparation for Redwood Server Installation
  • Database Prerequisites
  • Basic Sizing Guidelines
  • Planning

Installation

  • Installation
  • Download and Extract redwood-platform.zip
  • Installing Redwood Platform
  • Redwood Platform Application Server
  • Licensing Redwood Server

Security Overview

  • Security Overview
  • Security in Redwood Platform
  • External Security Systems
  • Lightweight Directory Access Protocol (LDAP)
  • Configuring LDAP Manually
  • Configuring LDAP With the LDAP Wizard
  • Database Authentication
  • Database Authentication - Enforcing Password Policies
  • Configuring JEE Security

Configuration

  • Installing and Configuring Redwood Platform Service on Windows
  • Submitting Processes and Licensing on Startup
  • Configuring the HTTP or HTTPS Interface of Redwood Platform
  • Configuring the APR HTTPS Interface of Redwood Platform
  • Configuring the NIO HTTPS Interface of Redwood Platform
  • Importing a Certificate Authority
  • Checking Your License
  • Managing Your Licenses with the License Manager
  • Configuration
  • Configuration Entries

Starting Automatically

  • Starting Redwood Platform Automatically
  • Starting Redwood Platform Automatically with Systemd
  • Starting Redwood Platform Automatically with Init
  • Starting Redwood Platform Automatically with Launchd
  • Starting Redwood Platform Automatically on Solaris

High Availability

  • High Availability
  • Configuring Web Application Clusters for High Availability
  • Creating Redwood Platform Clusters
  • Configuring Web Application Clusters on Microsoft Cluster Service
  • Configuring Platform Agents for High Availability
  • Configuring Platform Agents on Microsoft Cluster Service

Upgrade

  • Upgrading Redwood Server
  • Upgrading Redwood Platform

Migration

  • Migrating Redwood Platform

Uninstall

  • Uninstalling Redwood Server

Reference

  • Standard setvars script
  • Admin Server
  • Checking Your License
← Configuring the NIO HTTPS Interface of Redwood PlatformChecking Your License →

on-site-related topic Importing a Certificate Authority into your JVM Certificate Authority Store

You want to connect Redwood Server to remote servers over SSL/TLS that use self-signed certificates. You have signed these certificates with your Certificate Authority (CA). You retrieve the CA root certificate that you used for signing and import that into the CA store of your JVM.

To get the CA certificate file; ask the person who signed the certificate or if it is stored in a keystore, export it from the keystore.

warning

Always make sure that you can trust the certificate prior to importing!

note

The keytool and paths are the same on HP, IBM, and Oracle JVM's; the instructions do not differ for these platforms.

Prerequisites

  • The root CA certificate file must be available.
  • Installed and configured Java Development Kit (JDK), which should ideally be the latest version shipped by the platform vendor (it must be supported).

Procedure

Import the CA File into your JVM CA Store

  1. The keytool must be from the JVM used by your application server; if you have Redwood Server running in a cluster, you have to perform the following on each cluster node.
  2. Run the following command:
  3. keytool -cacerts -importcert -alias <some_alias> -file <file>.
  4. You will be prompted for the password. The default password is changeit.
  5. Run the following command to check the certificate has been imported successfully:
  6. keytool -list -keystore cacerts.

Change the Default Store Password

  1. The keytool must be from the JVM used by your application server; if you have Redwood Server running in a cluster, you have to perform the following on each cluster node.
  2. The command must be run as super-user or Administrator.
  3. keytool -storepasswd -keystore cacerts.
  4. You will be prompted for the password. The default password is changeit. You will be prompted to specify the new password twice, to make sure you make no typo.

Exporting a Certificate from a keystore

  1. From the command line, perfom the following command.
  2. keytool -exportcert -alias <alias> -file <file>.cer {-keystore <keystore> | -cacerts}.
  3. <alias> - the alias you specified when you created the keystore.
  4. <file> - the output file name.
  5. <keystore> - the keystore which you used to sign the original certificate, use -cacerts to import into the cacerts store.

See Also

  • Oracle JVM keytool Documentation

onsiteTopic

← Configuring the NIO HTTPS Interface of Redwood PlatformChecking Your License →
  • Prerequisites
  • Procedure
  • See Also
Docs
Getting StartedInstallationFinance InstallationConcepts
TroubleshootingArchiving
Learn and Connect
Support Portal
BlogEventsResources
ISO/ IEC 27001 Information Security Management
Automate to be human

2023 All Rights Reserved |

Terms of Service | Policies | Cookies | Glossary | Third-party Software | Contact | Copyright | Impressum |