The discovery process for reverse connect does not serve the same purpose as the discovery process for normal connections because reverse connections require the Serverto be configured to automatically attempt to connect to the Clientand the Clientto be configured so it knows what to do with the Serverwhen it receives the connection. The limited mechanisms discussed here may help SecurityAdminswith the configuration of Servers.

A SecurityAdmintasked with configuring Serversneeds to determine the ClientUrlsfor Clientsthat support reverse connect.

The following choices are available:

The mechanisms based on an LDS are not available since Clientsdo not register with the LDS.

Every Clientthat supports reverse connect has one or more ClientUrlsthat allow Serversto connect. Once the SecurityAdminacquires the ClientUrlvia an out-of-band mechanism, it can configure the Serverto use it.

A GDS is a Serverwhich allows other SecurityAdminsto search for Clients that support reverse connnect within the administrative domain of the GDS. The SecurityAdminuses the Callservice to invoke the QueryApplications Method (see 6.6.11) with “RCP” as aserverCapabilityFilterto get a list of Clientsthat support reverse connect from the GDS.

The discovery process is illustrated in Figure 5.


Figure 7– The Global Discovery Process for Reverse Connections

The ClientUrlsare returned in the DiscoveryUrlsparameter of the ApplicationDescriptionrecord and have the ‘rcp+’ prefix. DiscoveryUrls without the prefix are used for forward connections. Once the SecurityAdminhas a ClientUrlit can configure the Serverto use it.