james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tellier Benoit (JIRA)" <server-...@james.apache.org>
Subject [jira] [Resolved] (JAMES-1759) A web interface for JAMES administration
Date Tue, 14 Mar 2017 02:27:41 GMT

     [ https://issues.apache.org/jira/browse/JAMES-1759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Tellier Benoit resolved JAMES-1759.
    Resolution: Fixed

It have been implemented.

JAMES-1958 propose HTTPS
JAMES-1959 propose JWT
JAMES-1960 propose optional CORS support

https://issues.apache.org/jira/browse/JAMES-1931 propose implementing a front and adding new

> A web interface for JAMES administration
> ----------------------------------------
>                 Key: JAMES-1759
>                 URL: https://issues.apache.org/jira/browse/JAMES-1759
>             Project: James Server
>          Issue Type: New Feature
>    Affects Versions: master
>            Reporter: Tellier Benoit
>             Fix For: master
> We want to integrate James with other tool.
> Especially, we want that a remote programm create a domain and affiliated users.
> We would like to use non language specific APIs like JMX.
> User will be able to enable it / disable it from the configuration. Moreover, it will
be packaged with Guice.
> I propose to start with CRUD operations on users and domains, as proof of concept.
> I will also write an ASCII DOC document for information about this new API.
> It will use as a backend the same APIs than the JMX client.
> For now, I do not plan any security. For now, we are planning to use this feature either
in testing environments, or other linked containers.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

View raw message