RE: [mylar-dev] Re: Support queries that require login

["Mik Kersten" <beatmik@xxxxxxx>]

Your impatience is commendable Erkki :)

We should let Eugene respond to this, but it's great to see that you got
this working.  The challenge now, as always, is to simplify the UI some.  I
have put my suggestions on the bug.

151602: [Web connector] Support queries that require login
https://bugs.eclipse.org/bugs/show_bug.cgi?id=151602

Mik

> -----Original Message-----
> From: mylar-dev-bounces@xxxxxxxxxxx [mailto:mylar-dev-bounces@xxxxxxxxxxx]
> On Behalf Of Erkki Lindpere
> Sent: Saturday, November 18, 2006 9:24 AM
> To: Mylar developer discussions
> Subject: [mylar-dev] Re: Support queries that require login
> 
> Ok, so I wasn't patient enough to wait for feedback and already
> implemented this:
> 
> The latest patch to bug 151602 should be already somewhat usable, but
> contains a few UI layout problems:
> https://bugs.eclipse.org/bugs/attachment.cgi?id=54126
> 
> Screenshot of the new login configuration is here:
> https://bugs.eclipse.org/bugs/attachment.cgi?id=54128
> 
> On 11/16/06, Erkki Lindpere <villane@xxxxxxxxx> wrote:
> > Hi!
> >
> > Are you planning to address Bug #151602 before 1.0 ?
> > (https://bugs.eclipse.org/bugs/show_bug.cgi?id=151602 Support queries
> > that require login)
> >
> > This is the one and only thing that is currently stopping us from
> > using Mylar as is. Currently we are using a custom built CVS version
> > right after 0.8.0 that has the patch applied that I contributed to
> > that bug.
> >
> > If you are lacking cycles, I have some time this weekend that I could
> > spend on writing a new (and better) patch, but would someone be able
> > to review it next week or so and/or help me during/before creating the
> > patch because it's not that trivial:
> >
> > Basically what this patch would need to do is
> >
> > 1) to define the login request (usually it should be POST for security
> > reasons) there should be an UI for defining a HTTP request (URL,
> > Method, parameter name/value pairs should be enough) so I'm thinking
> > this could be abstracted to be usable elsewhere as well...
> > At request time, variable replacements must be done for the URL and
> > request parameters.
> >
> > 2) The UI also needs to define another regular expression: some login
> > pages generate a token that must be passed to the login request or the
> > login won't be successful. The token needs to be extracted from that
> > page.
> >
> > 3) maybe sometimes this login page could be on a separate URL from the
> > main repository URL so I'm not sure if there also needs to be a
> > repository parameter for the login page URL or could the main URL be
> > used instead
> >
> > I would like is to hear if this sounds good / acceptable before I
> > start creating the patch.
> >
> > Regards,
> > Erkki Lindpere
> >
> _______________________________________________
> mylar-dev mailing list
> mylar-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mylar-dev