[
https://issues.apache.org/jira/browse/SLING-3385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13897595#comment-13897595
]
Marius Petria commented on SLING-3385:
--------------------------------------
bq. avoid HTTP headers to transport any action or parameter
That will be done :).
bq. store the 'commands' in the content - IMO that's nonsense.
>From what I found out that is the only secure way in sling to expose REST APIs
>OOTB. Any servlet based approach (registered by path or by resourcetype) is
>unsecure by default and must be protected inside the servlet.
> Expose replication agents actions and information via HTTP.
> -------------------------------------------------------------
>
> Key: SLING-3385
> URL: https://issues.apache.org/jira/browse/SLING-3385
> Project: Sling
> Issue Type: Bug
> Components: Extensions
> Reporter: Marius Petria
> Labels: replication
>
> We need a safe way to expose replication agents actions via HTTP.
> Replication agents are OSGI services that can do the following actions:
> - replicate a content tree (build a content package and add it to a queue)
> - add a content package into a queue
> - remove a content package from its queue
> A replication agent also exposes information about packages in its queues.
> We have to expose all this actions and information over HTTP in order to be
> available to authorized users.
> Actions:
> - Replicate (schedules a replication action)
> POST /system/replication/agents
> X-replication-action: ADD/DELETE
> X-replication-path: /content/mycontent
> X-replication-agent: {agentName}
> - Import/Export (adds or removes a package from a queue)
> POST /system/replication/packages
> X-replication-action: PACKAGE_OFFER/PACKAGE_POLL
> X-replication-queue: {queueName}
> X-replication-agent: {agentName}
> -Information about agents, queues, packages
> GET /system/replication/agents?agent={agentName}
> GET /system/replication/queues?agent={agentName}
> GET /system/replication/packages?queue={queueName}&agent={agentName}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
