Thales e-Security KMIP Server is online

I did it again.  The port is  5696  not 5969.  I cut and pasted out of the RSA testing announcement email I sent last time.

Sorry for the confusion.

Bob L.
From:
 [mailto:]  On Behalf Of  Lockhart, Robert  Sent:  Friday, July 13, 2012 11:09 PM
To:  
Subject:  [kmip-interop-tech] Thales e-Security KMIP Server is online

The Thales KMIP server is now online. If you still have your credentials from the last interop test and have stated you are participating in this test, you can use the same credentials and the server will be available starting Monday if not sooner.  If you don't have credentials, haven't stated publicly you are testing or need the original set of credentials, contact me directly.

If you have any specific configuration requirements let me know those as well (e.g. required TCP port numbers other than 5696, etc...).

Our server IP Address is: 209.31.236.245
Server TCP Port: 5969 or 9022

If anyone needs something other than the default port or the higher port please let us know so we can configure additional TCP ports as needed.

The Thales server supports both KMIP 1.0 and 1.1 from the same appliance and all Tests supported by 1.0 are supported for the 1.1 use cases as well.

=======================================================================

Use cases supported by the Thales Server for KMIP 1.0 and KMIP 1.1 are:

=======================================================================

3.1.1 - Create / Destroy
3.1.2 - Register / Create / Get attributes / Destroy
3.1.3 - Create / Locate / Get / Destroy
3.1.4 - Dual client use-case, ID Placeholder linked Locate & Get batch
3.1.5 - Register / Destroy Secret Data
3.2   - Asynchronous Locate
4.1   - Revoke scenario
5.1   - Get usage allocation scenario
6.1   - Import of a Third-party Key
7.1   - Unrecognized Message Extension with Criticality Indicator false
7.2   - Unrecognized Message Extension with Criticality Indicator true
8.1   - Create a Key Pair
8.2   - Register Both Halves of a Key Pair
9.1   - Create a Key, Re-key
9.2   - Existing Key Expired, Re-key with Same lifecycle
9.3   - Existing Key Compromised, Re-key with same lifecycle
9.4   - Create key, Re-key with new lifecycle
9.5   - Obtain Lease for Expired Key
10.1  - Create a Key, Archive and Recover it
11.1  - Credential, Operation Policy, Destroy Date
12.1  - Query, Maximum Response Size

========================================================================

Additional use cases supported by the Thales Server for KMIP 1.1 are:

========================================================================

11.2  - Device Credential, Operation Policy, Destroy Date
12.2  - Query Vendor Extensions
13.1  - Asymmetric Register PKCS#1
13.2  - Asymmetric Register Certificate
13.3  - Create, Re-key Key Pair
13.4  - Register Key Pair, Certify and Re-certify Public Key
14.1  - Key Wrapping using AES Key Wrap and No Encoding
14.2  - Key Wrapping using AES Key Wrap with Attributes
15.1  - Locate a Fresh Object from the Default Group
15.2  - Client-side Group Management
16.1  - Discover Versions
17.1  - Handling of Attributes and Attributes Index Values
18.1  - Digests of Symmetric Keys
18.2  - Digests of RSA Private Keys

If anyone has any questions please contact me as soon as possible.

Bob L.

Robert A. (Bob)

Lockhart
Chief Solution Architect - Key Management
THALES e-Security, Inc.

-------------------------------------------------------

T:      +1 954 888 6245 (New Direct Number)
W:       www.thales-esecurity.com