Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Informatica ActiveVOS 9.2.5
  • All Products

Table of Contents

Search

  1. Preface
  2. Server User Guide
  3. Security Configurations
  4. Standard for Java-based Service Endpoints for Process Consumer (My Role) Partner Links
  5. Custom Invoke Handlers

Server User Guide

Server User Guide

Back Next

Security Configurations

Security Configurations

The OASIS WS-Security V1.0 (WSSE) standard establishes a framework for assuring the integrity and confidentiality of SOAP messages. Message integrity is assured via digital signature, and confidentiality of message data is achieved via encryption. The standards referenced by WS-Security V1.0 are supported by Process Server.
To use WS-Security features, you must set up the container in which Process Server is deployed with the necessary certificates manager or keystores that are often used for standard SSL processing. Also, you must provide a properties file that contains settings required for Process Server to interact with your platform’s encryption and certificate management. The properties file is named
crypto.properties
.
The following properties must be set in crypto.properties to match the your platform:
  • org.apache.ws.security.crypto.provider=<provider>
    where
    <provider>
     must be the default unless a custom provider is supplied that implements the apache crypto interface. The default is:
    org.apache.ws.security.components.crypto.Merlin
  • org.apache.ws.security.crypto.merlin.keystore.type=<type>
    The
    <type>
     is based on the format of the keystore, usually
    jks
     or
    pks12
    .
  • org.apache.ws.security.crypto.merlin.keystore.alias=<alias>
    The
    <alias>
     is the name that the private key and certificate are known by.
  • org.apache.ws.security.crypto.merlin.keystore.password=<password>
    where
    <password>
     is an optional property. Include a password if one is required for a keystore.
  • org.apache.ws.security.crypto.merlin.file=<keystore filename>
The keystore must be accessible by the server from the file system using the path specified by
org.apache.ws.security.crypto.merlin.file
 in
crypto.properties
. Also, the crypto.properties file must be available on the server's classpath. The target location of these files varies depending on the target platform.
The following is an example of crypto.properties: 
org.apache.ws.security.crypto.merlin.keystore.password=pw
org.apache.ws.security.crypto.merlin.keystore.type=jks
org.apache.ws.security.crypto.merlin.file=ae.keystore
org.apache.ws.security.crypto.provider=org.apache.ws.security.components.crypto.Merlin
org.apache.ws.security.crypto.merlin.keystore.alias=myadmin
0 COMMENTS
We’d like to hear from you!