Do we have any plans regarding when the console will be accessible to be served up from a HTTP API connection?

I have started to define the authentication mechanisms to be supported over HTTP so shortly we may want to start verifying GWT with these mechanisms but I think we may have issues if communicating with a different host to the one that made the console available.

Once I have a domain controller started how far off are we of being able to connect my web browser to that domain controller to run the admin console?

I may be able to get away with some testing using standalone and deploy using JBoss Web - what I am trying to test is that if the HTTP API starts prompting for SPNEGO authentication that the web browser will do what is needed. Regards, Darran Lofthouse. On 03/09/2011 02:32 PM, Heiko Braun wrote: > > > > On Mar 9, 2011, at 3:28 PM, Darran Lofthouse wrote: > >> Once I have a domain controller started how far off are we of being able to connect my web browser to that domain controller to run the admin console? > > > I would say 2-3 weeks probably. > But it depends on what you actually want to do with the console. > What use cases are you considering? > > /Ike _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

Do we have any plans regarding when the console will be accessible to be served up from a HTTP API connection? I have started to define the authentication mechanisms to be supported over HTTP so shortly we may want to start verifying GWT with these mechanisms but I think we may have issues if communicating with a different host to the one that made the console available. Regards, Darran Lofthouse. _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

Are you planning to use just the HTTP API or would you be using the Native / Remoting API?

Regards, Darran Lofthouse. On 03/09/2011 02:52 PM, Max Rydahl Andersen wrote: > Darran - I'm wondering which of all these various auth methods you are working > on we should support from the tools when starting/stopping/deploying/introspecting etc. > > ? > > basic username/password is trivial for us - anything above that I'm curious about. > > /max > > On Mar 9, 2011, at 14:42, Darran Lofthouse wrote: > >> Do we have any plans regarding when the console will be accessible to be >> served up from a HTTP API connection? >> >> I have started to define the authentication mechanisms to be supported >> over HTTP so shortly we may want to start verifying GWT with these >> mechanisms but I think we may have issues if communicating with a >> different host to the one that made the console available. >> >> Regards, >> Darran Lofthouse. >> _______________________________________________ >> jboss-as7-dev mailing list >> jboss-as7-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev > > /max > http://about.me/maxandersen > > >

>> Are you planning to use just the HTTP API or would you be using the Native / Remoting API? > > HTTP For HTTP the complete set being considered is 'BASIC, Digest, Certificate i.e. SSL and Kerberos/SPNEGO' - what are you using for your connections to the server? There is quite a bit of client side support for all these mechanisms in Java already. http://download.oracle.com/javase/6/docs/technotes/guides/net/http-auth.html

> Haven't seen any good usecases for using the native/remote api yet. I don't think the HTTP side will be too difficult to support but using Remoting will also automatically give you all of the supported mechanisms for the Native connections.

> /max > >> >> Regards, >> Darran Lofthouse. >> >> >> On 03/09/2011 02:52 PM, Max Rydahl Andersen wrote: >>> Darran - I'm wondering which of all these various auth methods you are working >>> on we should support from the tools when starting/stopping/deploying/introspecting etc. >>> >>> ? >>> >>> basic username/password is trivial for us - anything above that I'm curious about. >>> >>> /max >>> >>> On Mar 9, 2011, at 14:42, Darran Lofthouse wrote: >>> >>>> Do we have any plans regarding when the console will be accessible to be >>>> served up from a HTTP API connection? >>>> >>>> I have started to define the authentication mechanisms to be supported >>>> over HTTP so shortly we may want to start verifying GWT with these >>>> mechanisms but I think we may have issues if communicating with a >>>> different host to the one that made the console available. >>>> >>>> Regards, >>>> Darran Lofthouse. >>>> _______________________________________________ >>>> jboss-as7-dev mailing list >>>> jboss-as7-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev >>> >>> /max >>> http://about.me/maxandersen >>> >>> >>> >> > > /max > http://about.me/maxandersen > > >

>>> Haven't seen any good usecases for using the native/remote api yet. >> >> I don't think the HTTP side will be too difficult to support but using Remoting will also automatically give you all of the supported mechanisms for the Native connections. > > More automatically than using the http auth api ? The difference between native and http is that with native you get a java API that does all of the protocol stuff for you. With the HTTP API, you will have to do generate and parse JSON. For the web console we also allow for encoded DMR messages over HTTP, although if you are using DMR, thats about 80% of the java API.

>>>> Haven't seen any good usecases for using the native/remote api yet. >>> >>> I don't think the HTTP side will be too difficult to support but using Remoting will also automatically give you all of the supported mechanisms for the Native connections. >> >> More automatically than using the http auth api ? > > The difference between native and http is that with native you get a > java API that does all of the protocol stuff for you. With the HTTP API, > you will have to do generate and parse JSON. For the web console we also > allow for encoded DMR messages over HTTP, although if you are using DMR, > thats about 80% of the java API. when using this java api i still need to use the untyped model correct ? i.e. string based invocations or is it more typed ?

/max _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

>> For the web console we also >> allow for encoded DMR messages over HTTP, although if you are using DMR, >> thats about 80% of the java API. please forgive me being ignornat: what's DMR (google without luck so far)?