Description

GeoNode currently supports registering and importing resources from a fixed set of remote service types, such as WMS and ArcGIS services. These service types are defined statically in the service processor get_available_service_types.

This makes it difficult to register additional remote service types dynamically, while reusing the existing GeoNode Service and AuthConfig models.

The goal of this issue is to generalize remote service registration in GeoNode by introducing a dynamic service registry.

The registry should allow service types and their handlers to be registered in a common way. Existing GeoNode service types should continue to work as before.

This work should also generalize remote resource authentication handling so that remote resources can reuse AuthConfig consistently, instead of keeping authentication logic tied to a specific remote resource type such as WMS.

Proposed approach

• Introduce a dynamic service registry for remote service types.
• Register existing GeoNode service types through the registry.
• Allow additional service types and handlers to be registered dynamically.
• Keep existing service creation behavior working for WMS and ArcGIS services.
• Move common remote authentication payload handling from WMS-specific logic to the common remote resource handler.
• Allow remote resources to receive an AuthConfig either from the upload payload or from a matching registered remote service.

Expected outcome

GeoNode should provide a generic mechanism for registering remote service types and reusing authentication configuration for remote resources.