[rt-users] Rest API search by email?

2011-04-08 Thread elekistvan
Dear All,

I would need to use the rest api to query the tickets by e-mail address.
For eg, something like that: 
http://rt_host/rt/REST/1.0/search/ticket?query=OWNER.Email='elekist...@freemail.hu'
Is it possible to query tickets by email via rest api?

I would need to query these conditions:
my $tickets = new RT::Tickets($RT::SystemUser);
...
$tickets-FromSQL((status = 'new' or status = 'open') and  (Owner.EmailAddress 
= ' . $email . ' or Requestor.EmailAddress = ' . $email . ' or 
Cc.EmailAddress = ' . $email . ' or AdminCc.EmailAddress = ' . $email . ' 
or Watcher.EmailAddress = ' . $email . ' or QueueCc.EmailAddress = ' . 
$email . '  or QueueAdminCc.EmailAddress = ' . $email . '));
...

If currently this rest api query is not implemented, do you think the solution 
would be to extend the rest api? 
for eg: https://gist.github.com/737979
Is it difficult to do?

Thanks a lot,
Steve.



Re: [rt-users] Rest API search by email?

2011-04-08 Thread Christian Loos
You must use the right field name.
Try this:
http://rt_host/rt/REST/1.0/search/ticket?query=Owner.EmailAddress='elekist...@freemail.hu'

The best way would be to create the search with the query builder and
then copy and paste the query from the advanced tab to the REST url.

-Chris

Am 08.04.2011 08:16, schrieb elekistvan:
 Dear All,
 
 I would need to use the rest api to query the tickets by e-mail address.
 For eg, something like that: 
 http://rt_host/rt/REST/1.0/search/ticket?query=OWNER.Email='elekist...@freemail.hu'
 Is it possible to query tickets by email via rest api?
 
 I would need to query these conditions:
 my $tickets = new RT::Tickets($RT::SystemUser);
 ...
 $tickets-FromSQL((status = 'new' or status = 'open') and  
 (Owner.EmailAddress = ' . $email . ' or Requestor.EmailAddress = ' . 
 $email . ' or Cc.EmailAddress = ' . $email . ' or AdminCc.EmailAddress = 
 ' . $email . ' or Watcher.EmailAddress = ' . $email . ' or 
 QueueCc.EmailAddress = ' . $email . '  or QueueAdminCc.EmailAddress = ' . 
 $email . '));
 ...
 
 If currently this rest api query is not implemented, do you think the 
 solution would be to extend the rest api? 
 for eg: https://gist.github.com/737979
 Is it difficult to do?
 
 Thanks a lot,
 Steve.
 
 


[rt-users] Hugo Darley is out of the office.

2011-04-08 Thread Hugo Darley

I will be out of the office starting  04/04/2011 and will not return until
18/04/2011.

I will respond to your message when I return. Please contact
eu@instinet.co.uk in my absence
INSTINET - Setting the standards in agency execution

Disclaimer
This message contains confidential information and is intended only for the 
named individual. If you are not the named addressee, you should not 
disseminate, distribute or copy this e-mail. Please notify the sender 
immediately by e-mail if you have received this message in error and delete 
this e-message from your system. E-mail transmission cannot be guaranteed to be 
secure or error-free as information could be intercepted, corrupted, lost, 
destroyed, delayed in transmission, incomplete, or may contain viruses. The 
sender therefore does not accept liability for any errors or omissions in the 
contents of this message which arise as a result of e-mail transmission. If 
verification is required please request a hard-copy version. This message is 
provided for informational purposes and should not be construed as a 
solicitation or offer to buy or sell any securities or related financial 
instruments.



Re: [rt-users] Rest API search by email?

2011-04-08 Thread elekistvan
Hi Christian,

Thanks for the answer. I tried all version of the query, but I always got 'No 
matching results.' answers. However, I am pretty sure, that there are tickets 
what would match for these queries:

http://rt_host/rt/REST/1.0/search/ticket?query=Owner.EmailAddress='elekist...@freemail.hu'

or

http://rt_host/rt/REST/1.0/search/ticket?query=Owner='elekist...@freemail.hu'

so, for eg. this is working: 
http://rt_host/rt/REST/1.0/search/ticket?query=Status='new'

The user names and the e-mail addresses are the same, that's why i would expect 
valid answers. My rt version is:  RT 3.8.5

Is this user list query is implemented in this version of this rest api?
Or what do you think I am doing wrong?

Thanks a lot!
Nice weekend.


  Christian Loos cl...@netcologne.de, ezt írta: 
  
  You must use the right field name.
Try this:
http://rt_host/rt/REST/1.0/search/ticket?query=Owner.EmailAddress='elekist...@freemail.hu'

The best way would be to create the search with the query builder and
then copy and paste the query from the advanced tab to the REST url.

-Chris

Am 08.04.2011 08:16, schrieb elekistvan:
 Dear All,
 
 I would need to use the rest api to query the tickets by e-mail address.
 For eg, something like that: 
 http://rt_host/rt/REST/1.0/search/ticket?query=OWNER.Email='elekist...@freemail.hu'
 Is it possible to query tickets by email via rest api?
 
 I would need to query these conditions:
 my $tickets = new RT::Tickets($RT::SystemUser);
 ...
 $tickets-FromSQL((status = 'new' or status = 'open') and  
 (Owner.EmailAddress = ' . $email . ' or Requestor.EmailAddress = ' . 
 $email . ' or Cc.EmailAddress = ' . $email . ' or AdminCc.EmailAddress = 
 ' . $email . ' or Watcher.EmailAddress = ' . $email . ' or 
 QueueCc.EmailAddress = ' . $email . '  or QueueAdminCc.EmailAddress = ' . 
 $email . '));
 ...
 
 If currently this rest api query is not implemented, do you think the 
 solution would be to extend the rest api? 
 for eg: https://gist.github.com/737979
 Is it difficult to do?
 
 Thanks a lot,
 Steve.
 
 



Re: [rt-users] RT::Authen::ExternalAuth, Possible Configuration Issue?

2011-04-08 Thread Eli Guzman
Original Message
From: rt-users-boun...@lists.bestpractical.com
[mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of Thomas
Sibley Sent: Thursday, April 07, 2011 6:33 PM To:
rt-users@lists.bestpractical.com Subject: Re: [rt-users]
RT::Authen::ExternalAuth,Possible Configuration Issue? 

 On 04/07/2011 08:04 PM, Eli Guzman wrote:
 == TL/DR ==
 
 Installed RT 3.8.9 on a test RHEL server, and cannot seem to get
 RT::Authen::ExternalAuth to properly work, please help!
 
 Sorry for the bump to this topic, just needed to see if anyone can
 still assist with this issue. If this is a problem with the module
 itself, what would be another possible workaround for getting LDAP
 connected?
 
 You didn't actually include the log or configuration files that you
 said you did.  However I suspect you're running version 0.08 of
 ExternalAuth which is known not to work with RT 3.8.9.  You should
 download and install ExternalAuth 0.08_01 from CPAN at the link
 below.  0.08_01 is a developer release containing a known fix for the
 problem. 
 

http://search.cpan.org/CPAN/authors/id/F/FA/FALCONE/RT-Authen-ExternalAu
th-0.08_01.tar.gz
 
 Thomas

Hey Thomas,

Thanks a lot for the information, I went ahead and queried the cpan
packages and you are 
correct I am running: 

   RT::Authen::ExternalAuth  0.08

I will give try at downloading 0.08_01 and see how it goes. I did
include the logs
in another email, not sure if that one made the list. I am including the
logs on this 
email (just in case anyone wants a quick glance at them), please do let
me know if they 
do not go through (sometimes our AV server strips off attachments). If
they don't I'll 
just do a pastebin from the logs I do have. I'll make sure to update the
list with the
results.

Thanks,
Eli


config-and-logs.tar.gz
Description: config-and-logs.tar.gz


[rt-users] Is it possible to search for non-bookmarked tickets?

2011-04-08 Thread Jon Baker
I see that if I put id='__Bookmarked__' in the search query, it shows my 
bookmarked tickets.  Is it possible to do the opposite - show tickets that are 
not bookmarked?  What I'm wanting to be able to do is create a saved search 
underneath my bookmarked tickets on my home page, where between the bookmarked 
tickets and this second search I have all tickets assigned to me, but no ticket 
is in both lists.  I tried id != '__Bookmarked__' but that seems to be pulling 
up everything, even bookmarked tickets.  Thoughts?
-- 
Jon Baker
Systems Administrator
Church on the Move
1003 N 129th E Ave
Tulsa OK 74116
(918) 234-5656




CONFIDENTIALITY NOTICE: This transmission may be confidential and subject to 
legal privilege.  If you are not the intended recipient of this message, you 
may not review, disclose, print, copy or disseminate this information. If you 
have received this in error, please reply and notify the sender (only) and 
delete the message. Unauthorized interception of this e-mail is a violation of 
federal criminal law.


Re: [rt-users] Rest API search by email?

2011-04-08 Thread Thomas Sibley
On 04/08/2011 11:20 AM, elekistvan wrote:
 Hi Christian,
 
 Thanks for the answer. I tried all version of the query, but I always got 'No 
 matching results.' answers. However, I am pretty sure, that there are tickets 
 what would match for these queries:
 
 http://rt_host/rt/REST/1.0/search/ticket?query=Owner.EmailAddress='elekist...@freemail.hu'
 
 or
 
 http://rt_host/rt/REST/1.0/search/ticket?query=Owner='elekist...@freemail.hu'
 
 so, for eg. this is working: 
 http://rt_host/rt/REST/1.0/search/ticket?query=Status='new'

If those are the actual URLs you're using, you're not properly encoding
the value of the query parameter.  At the very least in the cases above,
= needs to be escaped as %3D.

Thomas

 The user names and the e-mail addresses are the same, that's why i would 
 expect valid answers. My rt version is:  RT 3.8.5
 
 Is this user list query is implemented in this version of this rest api?
 Or what do you think I am doing wrong?
 
 Thanks a lot!
 Nice weekend.
 
 
   Christian Loos cl...@netcologne.de, ezt írta: 
   
   You must use the right field name.
 Try this:
 http://rt_host/rt/REST/1.0/search/ticket?query=Owner.EmailAddress='elekist...@freemail.hu'
 
 The best way would be to create the search with the query builder and
 then copy and paste the query from the advanced tab to the REST url.
 
 -Chris
 
 Am 08.04.2011 08:16, schrieb elekistvan:
 Dear All,

 I would need to use the rest api to query the tickets by e-mail address.
 For eg, something like that: 
 http://rt_host/rt/REST/1.0/search/ticket?query=OWNER.Email='elekist...@freemail.hu'
 Is it possible to query tickets by email via rest api?

 I would need to query these conditions:
 my $tickets = new RT::Tickets($RT::SystemUser);
 ...
 $tickets-FromSQL((status = 'new' or status = 'open') and  
 (Owner.EmailAddress = ' . $email . ' or Requestor.EmailAddress = ' . 
 $email . ' or Cc.EmailAddress = ' . $email . ' or AdminCc.EmailAddress = 
 ' . $email . ' or Watcher.EmailAddress = ' . $email . ' or 
 QueueCc.EmailAddress = ' . $email . '  or QueueAdminCc.EmailAddress = ' . 
 $email . '));
 ...

 If currently this rest api query is not implemented, do you think the 
 solution would be to extend the rest api? 
 for eg: https://gist.github.com/737979
 Is it difficult to do?

 Thanks a lot,
 Steve.


 



Re: [rt-users] RT::Authen::ExternalAuth, Possible Configuration Issue?

2011-04-08 Thread Eli Guzman
Original Message
From: rt-users-boun...@lists.bestpractical.com
[mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of Eli
Guzman Sent: Friday, April 08, 2011 10:36 AM To: Thomas Sibley;
rt-users@lists.bestpractical.com Subject: Re: [rt-users]
RT::Authen::ExternalAuth,Possible Configuration Issue? 

 Original Message
 From: rt-users-boun...@lists.bestpractical.com
 [mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of Thomas
 Sibley Sent: Thursday, April 07, 2011 6:33 PM To: 
 rt-users@lists.bestpractical.com Subject: Re: [rt-users]
 RT::Authen::ExternalAuth,Possible Configuration Issue? 
 
 On 04/07/2011 08:04 PM, Eli Guzman wrote:
 == TL/DR ==
 
 Installed RT 3.8.9 on a test RHEL server, and cannot seem to get
 RT::Authen::ExternalAuth to properly work, please help!
 
 Sorry for the bump to this topic, just needed to see if anyone can
 still assist with this issue. If this is a problem with the module
 itself, what would be another possible workaround for getting LDAP
 connected?
 
 You didn't actually include the log or configuration files that you
 said you did.  However I suspect you're running version 0.08 of
 ExternalAuth which is known not to work with RT 3.8.9.  You should
 download and install ExternalAuth 0.08_01 from CPAN at the link
 below. 
 0.08_01 is a developer release containing a known fix for the
 problem. 
 
 

http://search.cpan.org/CPAN/authors/id/F/FA/FALCONE/RT-Authen-ExternalAu
 th-0.08_01.tar.gz
 
 Thomas
 
 Hey Thomas,
 
 Thanks a lot for the information, I went ahead and queried the cpan
 packages and you are correct I am running: 
 
RT::Authen::ExternalAuth  0.08
 
 I will give try at downloading 0.08_01 and see how it goes. I did
 include the logs in another email, not sure if that one made the
 list. I am including the logs on this email (just in case anyone
 wants a quick glance at them), please do let me know if they do not
 go through (sometimes our AV server strips off attachments). If they
 don't I'll just do a pastebin from the logs I do have. I'll make sure
 to update the list with the results.  
 
 Thanks,
 Eli

I went ahead and updated RT::Authen::ExternalAuth to version 0.8_01, 
but for some reason I am still getting the same error as before:

[Fri Apr  8 23:34:13 2011] [debug]: Attempting to use external auth
service: 
My_LDAP
(/opt/rt3/local/plugins/RT-Authen-ExternalAuth/lib/RT/Authen/ExternalAut
h.pm:64)
[Fri Apr  8 23:34:13 2011] [debug]: SSO Failed and no user to test with.
Nexting 
(/opt/rt3/local/plugins/RT-Authen-ExternalAuth/lib/RT/Authen/ExternalAut
h.pm:92)
[Fri Apr  8 23:34:13 2011] [debug]: Autohandler called ExternalAuth.
Response: 
(0, No User)
(/opt/rt3/local/plugins/RT-Authen-ExternalAuth/html/Elements/DoAuth:26)

So I am not sure what else could be causing the issue, I am guessing
that
this is a configuration issue at this point (as to where exactly the
issue
may be, that is the 64,000 dollar question). 

I'll continue to have a look and see if I can fix the issue, but I think

I may have to use an alternate method of connecting to AD (i.e. OpenLDAP

Synchronization from our AD server, or a manual overlay). If there is
any additional 
insight on the problem please feel free to reply, as I'd be willing to
try other solutions 
as needed.

Thanks,
Eli