[
https://issues.apache.org/jira/browse/GUACAMOLE-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15990028#comment-15990028
]
Michael Jumper commented on GUACAMOLE-289:
------------------------------------------
It might be nice to extend this further, such that all resources exposed
through the REST API can have an optional subresource at {{ext}}, thus avoiding
the need for extensions to reimplement the existing hierarchy.
> Add support for declaring REST services within extensions
> ---------------------------------------------------------
>
> Key: GUACAMOLE-289
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-289
> Project: Guacamole
> Issue Type: New Feature
> Components: guacamole, guacamole-ext
> Reporter: Michael Jumper
> Assignee: Michael Jumper
>
> Though Guacamole extensions can modify JavaScript, HTML, expose static
> resources, etc., they are not able to expose custom REST services. This
> limits the ability of extensions to provide functionality which depends on
> services unrelated to maintenance of users or connections, as well as
> functionality which may not currently be covered by the extension API.
> Extensions should be able to:
> # Expose REST resources/services which do not require authentication
> # Expose REST resources/services which *do* require authentication (require
> an associated auth token)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
