Operations Guide

10.5 HotFix 1
- 10.5
- 10.2 HotFix 1
- 10.2
- 10.1 HotFix 1
- 10.1
- 10.0 HotFix 1
- 10.0

Back Next

Web Services Security

MDM Registry Edition Web Services supports the Web Services Security: SOAP Message Security 1.1 (WS-Security 2004) OASIS Standard Specification dated 1 February 2006.

Web Server Authentication

You can use a private key or a user name token to authenticate a connection between a client and a web server.

Private Key

To deploy this method, start the servers by running the following script:

On UNIX.

$SSABIN/idsup

On Windows.

%SSABIN%\idsup.bat

You can use the following options with the script:

-qa1.0: Specifies to use WS-Addressing 1.0.
-qs1.1: Specifies to use WS-Security 1.1.
-qsrFile3: Specifies a PEM file that contains an X509 root certificate.

User Name Token

To deploy this method, start the servers by running the following script:

On Unix.

$SSABIN/idsup

On Windows.

%SSABIN%\idsup.bat

You can use the following options with the script:

-qa1.0: Specifies to use WS-Addressing 1.0.
-qs1.1: Specifies to use WS-Security 1.1.
-qsu<username>: Specifies that the server requires a user name token. Enter the user name and password in the MDM Registry Edition dictionary.; Use the
iirdict
utility to add a user name to the dictionary.; For example, the following sample command adds the user name Jack to the dictionary:; iirdict testx528.dir\testx528.dic iirdict> May 17 2022 15:52:38 10.3.0.000 Operating on 'testx528.dir\testx528.dic' Enter password: Command (a=Add d=Delete l=List t=Test q=Quit)? a Enter alias: Jack Enter connection details: Type (odb): user User password: Secret iirdict> alias 'Jack' added successfully Command (a=Add d=Delete l=List t=Test q=Quit)? l # 2022-05-25 11:44:53.005000 mtaylor Created # 2022-05-25 11:50:39.837696 mtaylor Added alias 'Jack' Command (a=Add d=Delete l=List t=Test q=Quit)?

You can also use the HTTP authentication method. For more information on HTTP authentication, see Conventions.

Transport Layer Security

MDM Registry Edition web services can employ HTTPS to implement Transport Layer Security. This will provide point to point security. To deploy this facility on, start the servers by running the shell script

$SSABIN/idsup

on Unix or the batch script

%SSABIN%\idsup.bat

on Windows with the following options:

-qcFile1: Specifies the PEM file containing an X509 certificate.
-qkFile2: Specifies the PEM file containing an RSA private key.
-qrFile3: Specifies the PEM file containing an X509 root certificate.

The web service will now use HTTPS instead of HTTP. HTTPS sends HTTP messages using SSL, a well established and widely available security protocol. If HTTPS is specified, any messages sent to the web service using HTTP will be discarded.

You must specify all the three options. The server will report an error on startup if one is omitted.

Samples

The

ws-sample3.cs

sample file requires Web Services Enhancements (WSE) 3.0 and uses a specified X509 RSA certificate to create a message signed with a private key.

The MDM Registry Edition servers use the specified public RSA key to validate the request.

Use the following sample Java files to connect to the XML Search Server:

HTTPSample.java

for HTTP authentication

HTTPSSample.java

for HTTPS authentication

The sample programs are located in the following directory:

<installation directory>\samples\programs\java-xml

Web Services

Download Guide

Watch

Comments

Communities

Knowledge Base

Success Portal

0 COMMENTS

We’d like to hear from you! Log in to comment.

Rename Saved Search

Table of Contents

Operations Guide

Operations Guide

Web Services Security

Web Services Security

Web Server Authentication

Private Key

User Name Token

Transport Layer Security

Samples