 |
Domain Name Services
|
 |
|
EPP Software Development Kits
VeriSign offers
multiple EPP 1.0 Software Development Kits (SDK’s) for integration with
the Name Store platform, the COM NET Registry, the NAME Registry, and
for use with non-VeriSign Registries that implement to the EPP 1.0 RFC’s.
The EPP 1.0 RFC’s include:
- RFC
4930 – Extensible Provisioning Protocol
- RFC
4931 - Extensible Provisioning Protocol (EPP) Domain Name Mapping
- RFC
4932 - Extensible Provisioning Protocol (EPP) Host Mapping
- RFC
4933 - Extensible Provisioning Protocol (EPP) Contact Mapping
- RFC
4934 - Extensible Provisioning Protocol (EPP) Transport Over TCP
The SDK’s are provided
in either Java or C++, where the EPP mappings and extensions supported
by each language varies. The Java SDK is built from a single core
called “gen” (short for general) that implements RFC 4930 and RFC 4934.
Each additional mapping or extension can be built and packaged separated
but are grouped into “bundle” distributions for convenience.
Additional mappings and extensions can be added to a “bundle” distribution
to form a configuration that meets your integration requirements.
The “bundle” distributions include:
- Name Store / SRS Bundle – Includes all of the mappings
and extensions for integration with the Name Store platform and the
COM NET Registry.
- NAME Bundle – Includes all of the mappings and extensions for integration
with the NAME Registry
VeriSign has created a C++ EPP-RTK add-on for the COM NET Registry
that is available from the Sourceforge EPP-RTK
web page. The COM NET RTK C++ Add-on is dependent on the usage of EPP-RTK-CPP
0.9.2.
The following table
maps the EPP mappings and extensions to the supporting EPP distributions. Bolded items are new or updated.
Name Store
/ SRS Bundle Software Development Kits
The following table
includes the supported Name Store / SRS Bundle Software Development
Kits for interfacing with the Name Store platform and the COM NET Registry.
|
|
|
|
3.8.0.2 |
Unix
Binary
Unix
Source
Windows
Binary
Windows
Source |
Programmer’s
Guide
Change
Log |
- Added
RFC 4310 - DNSSEC Extension
- Added
Session Pool iniMaxActive property to have the pool pre-create the maxActive
sessions upon initialization.
- Added
Session Pool borrowRetries property to include a built in retry on creating
a new session in the pool.
- Added
support for Name Suggestion language element in the command and response.
- Change
default load order of EPPHostMapFactory and EPPDomainMapFactory to remove
an error based on the dependency between domain-1.0.xsd to host-1.0.xsd.
- Fixed
issue where the XML Parser Pool needs to be initialized after the CODEC
to properly pre-load all of the dependent XML schemas.
- Added
support for an asynchronous EPPSession mode (MODE_ASYNC) for pipelining
commands.
- Added
missing com.verisign.epp.serverstub.ContactPollHandler from the EPP.PollHandlers
property of epp-http.config.
|
3.7.0.3 |
Unix
Binary
Unix
Source
Windows
Binary
Windows
Source
|
Programmer’s
Guide
Change
Log |
- Removed
RCC entries from the NameStore Bundle default configuration and test
code
- Removed
CLS from the bundle
- Added
the JobsContact extension to the bundle
- Added
Contact to bundle
- Added
the EPPSession.getClientCon() method and made the EPPSSLClientSocket.getSocket()
method public to support SSL Re-negotiation.
- Added
the EPP.MaxPacketSize configuration property to override the EPPXMLStream
maximum packet size that was previous defined by the constant MAX_PACKET_SIZE.
The EPPXMLStream.MAX_PACKET_SIZE has been renamed to EPPXMLStream.DEFAULT_MAX_PACKET_SIZE
and used if the EPP.MaxPacketSize property is not set.
- Added
support for specifying a period of 0 to match the EPP specification
as identified in SR 1288144.
- Added
"getXmlSchemas() : Set" method to EPPFactory, EPPMapFactory,
EPPExtFactory, and the derived classes of EPPMapFactory and EPPExtFactory
to specify the XML schemas that need to be pre-loaded to support the
latest EPP RFC’s
|
3.6.1.0 |
Unix
Binary
Unix
Source
Windows
Binary
Windows
Source
|
Programmer’s
Guide
Change
Log |
- Updated
the Programmer’s Guide
- Added
support for separate SSL configurations per session pool. This
is not supported for HTTPS.
- Support
for RCCTLD Transfers
- Removed
references to EU Sunrise RCCTLD Extension
- Support
for setting authInfo for all transfer commands
- Fixed
a connection leak within the session pool when there is a failure during
EPPSession.initSession.
- Updated
EPPSessionPool.returnObject(EPPSession) to check that the session
is not null prior to returning to ensure that the numActive does not
go negative.
- Added
support for specifying the SSL enabled protocols and enabled cipher
suites.
|
3.5.1.0 |
Unix
Binary
Unix
Source
Windows
Binary
Windows
Source
|
Programmer’s
Guide
Change
Log |
- Explicitly
set the pool minEvictableIdleTimeMillis configuration property
- Fix
SR #907237
- Javadoc
updates to the Name Suggestion Product
|
3.5.0.0 |
Unix
Binary
Unix
Source
Windows
Binary
Windows
Source
|
Programmer’s
Guide
Change
Log |
- Added
Name Suggestion
|
NAME Bundle
Software Development Kits
The following table
includes the supported NAME Bundle Software Development Kits
|
|
|
|
1.2.0.2 |
Unix
Binary
Unix
Source
Windows
Binary
Windows
Source |
Readme
Install
Change
Log |
- Added
Session Pool iniMaxActive property to have the pool pre-create the maxActive
sessions upon initialization.
- Added
Session Pool borrowRetries property to include a built in retry on creating
a new session in the pool.
- Change
default load order of EPPHostMapFactory and EPPDomainMapFactory to remove
an error based on the dependency between domain-1.0.xsd to host-1.0.xsd.
- Fixed
issue where the XML Parser Pool needs to be initialized after the CODEC
to properly pre-load all of the dependent XML schemas.
- Added
support for an asynchronous EPPSession mode (MODE_ASYNC) for pipelining
commands.
|
1.1.1.0
|
Unix
Binary
Unix
Source
Windows
Binary
Windows
Source
|
Readme
Install
Change
Log |
- Added
"getXmlSchemas() : Set" method to EPPFactory, EPPMapFactory,
EPPExtFactory, and the derived classes of EPPMapFactory and EPPExtFactory
to specify the XML schemas that need to be pre-loaded.
- Added
the EPP.MaxPacketSize configuration property to override the EPPXMLStream
maximum packet size that was previous defined by the constant MAX_PACKET_SIZE.
The EPPXMLStream.MAX_PACKET_SIZE has been renamed to EPPXMLStream.DEFAULT_MAX_PACKET_SIZE
and used if the EPP.MaxPacketSize property is not set.
- Added
support for specifying a period of 0 to match the EPP specification
as identified in SR 1288144.
- Added
diagnostic logs to EPPSession to better track information associated
with the state of the session
- Added
EPPSessionPoolTst.testCloseSession() test and added a supporting change
to GenHandler to test the server closing the connection before the client.
|
1.1.0.0 |
Unix
Binary
Unix
Source
Windows
Binary
Windows
Source |
Readme
Install
Change
Log |
- Added
setting the authInfo for all Domain, EmailFwd, DefReg, and NameWatch
transfer commands.
In sync with Name Store / SRS Bundle 3.6.1.0. |
1.0.3.0 |
Unix
Binary
Unix
Source
Windows
Binary
Windows
Source |
Readme
Install
Change
Log |
- Explicitly
set the pool minEvictableIdleTimeMillis configuration property
- Fix
SR #907237
- Javadoc
updates to the Name Suggestion Product
|
Contact
Mapping Add-on Software Development Kits
The following table
includes the supported Contact Mapping Add-on Software Development Kits
Note: This Development
Kit is deprecated and should not be used with the NameStore / SRS Bundle
past version 3.6.1.0 since the NameStore / SRS Bundle includes the Contact
Mapping.
Protocol
Tool
The Protocol Tool
is a Java Client that can connect to multiple environments (OT&E,
Production, EPP SDK Stub Server) with a set of customizable templates
and with three menu layouts. The layouts supported include Name
Store, SRS (COM/NET), and NAME. The Protocol Tool can connect
to servers using multiple transports in parallel (EPP/SSL, EPP/TCP,
EPP/HTTPS, EPP/HTTP). It requires Java 1.4 or higher and requires
an official Java Keystore for connecting to OT&E or Production.
EPP Tool
The EPP Tool below
is our interactive tool to be used for development and troubleshooting.
The tool is designed to behave as though it is a Registrar application
in the OT&E environment. Provided along with the Tool are a set
of definitive, context-based interactive examples intended to help a
developer create and troubleshoot their code design. The EPP Tool
supports both the Name Store platform and the COM NET Registry (Core).
EPP
Tool
|