I believe it was in the works but cant hurt to add it to the jira as a feature request.
On Sat, 24 Dec 2016 at 22:04 Brandon Brinkley <brinkle...@gmail.com> wrote: > This is timely, as I have just recently renewed my interest in Wave with > the idea of potentially bundling it with a few other services that could be > useful for small teams (e.g. students, auditors, etc.). I haven't had a > chance to look at it much yet, but I would want to either share the > authentication, or at least be able to pass through the credentials. Also, > I it would be useful to be authenticate against AD if that isn't already > possible. > > Thanks! > -Brandon > > On Saturday, December 24, 2016, Evan Hughes <wisebald...@apache.org> > wrote: > > > Hello All, > > > > Just wanting to get some feedback from the community as I start rewriting > > the client and the api behind it (to replace the Gwt code in the repo and > > the current servlets). > > > > http://localhost:9898/api/auth/login?format=json > > http://localhost:9898/api/auth/login?format=protobuf > > http://localhost:9898/api/auth/login // defaults to the protobuf > > > > currently using url's like the ones above with a response like: > > > > { > > "email": true > > } > > which states that email authentication is available (allows us to add > > oauth providers latter). The change of URL is due to using client side > > frameworks (Angular 2) instead of GWT to achieve the UI which will be > > at a non /api/ route. This also lets the server be more easily > > configured to be of use to SwellRT and other projects as our client > > isn't part of the backend anymore and the server is an abstract > > element.Ive also made the source for this endpoint at > > /wave/src/main/java/org/apache/wave/server/api/v1/LoginServlet.java so > > that we can remove dead code as we transition into one naming scheme > > instead of the 3 that exist atm. > > > > ~ Evan Hughes > > > > > -- > Thanks! > -Brandon >
