[rt-users] How to create ticket without log in using CommandBy MAil

2016-01-15 Thread vahid Khorasani via rt-users 
--- Begin Message ---

Hi
I' m working on a project to let lots of external users to create 
tickets anytime the deal with a problem and my support team start 
working on it to solve it ,but I don't have any user accounts for them 
neither in my RT local database nor in my LDAP ( and absolutely I don't 
wanna have any ;-) ).
I installed CommandByMail extension on my RT and I also enabled it in my 
RT_SiteConfig.pm file but it doesn't work.

I have two questions:
1-To whom these external users must send their mail (I mean what email 
address)??

2-Should I add anything special in my RT_SiteConfig.pm ??
--- End Message ---

Re: [rt-users] "RT::Authen::ExternalAuth".

2016-01-15 Thread ggamache 
thank you for your help 
I tried set ($AuthMethods, ['LDAP' , 'My_MySQL']); but It seem I had to add a 
new part in the ExternalSettingsSet($ExternalSettings, {  'My_LDAP' 
 'My_MySQL...'
If I add Internal I still have to do this part or it somehow find it 
automatically? 
 
regards,
Ghislain
Date: Fri, 15 Jan 2016 08:38:47 -0700
From: ml-node+s8502n6119...@n7.nabble.com
To: ghislaingama...@hotmail.com
Subject: Re: "RT::Authen::ExternalAuth".



Hi
That's the concern that I had about one month ago , but I totally solved it and 
I 'll be glad to help you solve it sooner that I could :)
Yes you can have both of them at the same time by adding the following line in 
your RT_SiteConfig.pm:
set ($AuthMethods, ['LDAP' , Internal']);

I,ll be happy if you let me know the result 
Good LuckFrom: [hidden email]
Sent: ‎15/‎01/‎2016 17:28
To: [hidden email]
Subject: [rt-users] "RT::Authen::ExternalAuth".

Question on "RT::Authen::ExternalAuth".
I've set the ExternalAuth and it worked
Is there a way to have both auth External and still be able to log with the
internal DB ? 

regards,
Ghis





--
View this message in context: 
http://requesttracker.8502.n7.nabble.com/RT-Authen-ExternalAuth-tp61193.html
Sent from the Request Tracker - User mailing list archive at Nabble.com.











If you reply to this email, your message will be added to the 
discussion below:

http://requesttracker.8502.n7.nabble.com/RT-Authen-ExternalAuth-tp61193p61196.html



To unsubscribe from "RT::Authen::ExternalAuth"., click here.

NAML
  



--
View this message in context: 
http://requesttracker.8502.n7.nabble.com/RT-Authen-ExternalAuth-tp61193p61197.html
Sent from the Request Tracker - User mailing list archive at Nabble.com.

Re: [rt-users] "RT::Authen::ExternalAuth".

2016-01-15 Thread Vahid Khorasani via rt-users 
--- Begin Message ---
Hi
That's the concern that I had about one month ago , but I totally solved it and 
I 'll be glad to help you solve it sooner that I could :)
Yes you can have both of them at the same time by adding the following line in 
your RT_SiteConfig.pm:
set ($AuthMethods, ['LDAP' , Internal']);

I,ll be happy if you let me know the result 
Good Luck

-Original Message-
From: "ggamache" 
Sent: ‎15/‎01/‎2016 17:28
To: "rt-users@lists.bestpractical.com" 
Subject: [rt-users] "RT::Authen::ExternalAuth".

Question on "RT::Authen::ExternalAuth".
I've set the ExternalAuth and it worked
Is there a way to have both auth External and still be able to log with the
internal DB ? 

regards,
Ghis





--
View this message in context: 
http://requesttracker.8502.n7.nabble.com/RT-Authen-ExternalAuth-tp61193.html
Sent from the Request Tracker - User mailing list archive at Nabble.com.
--- End Message ---

Re: [rt-users] Attaque de type CSRF possible

2016-01-15 Thread Emmanuel Lacour 
Le 13/01/2016 10:00, wajdi a écrit :
> 
>   Hi,
> 

hi,

> 
>   Attaque de type CSRF possible
> 
> RT a détecté qu'une attaque de type *CSRF* était possible pour cette
> requête, en raison de L'en-tête "Referrer" envoyée par votre navigateur
> (x.x.x.x:80) n'est pas autorisé par la configuration de RT
> (127.0.0.1:80). Un attaquant malicieux et peut-être en train d'essayer
> de *mettre à jour un ticket* à votre place.Si vous n'êtes pas à
> l'origine de cette requête, alors vous devriez alerter votre responsable
> sécurité.
> 
> Si vous souhaitiez vraiment visiter /Ticket/Update.html et mettre à jour
> un ticket, alors *cliquez ici pour poursuivre votre demande
> *.
> 
> Notice : i use rt4.2.12
> 
> Please help me, how can i resolve this error.
> 
>

You acceded to your RT with url http://196.203.79.151/ but you're RT
configuration as another $WebDomain set (127.0.0.1).

you should acces using the ocnfigured web domain or set
$ReferrerWhitelist or disable CRSF protection.

Explained in details here:
https://bestpractical.com/docs/rt/4.2/RT_Config.html#Extra-security
(RestrictReferrer and ReferrerWhitelist)


-- 
Easter-eggs  Spécialiste GNU/Linux
44-46 rue de l'Ouest  -  75014 Paris  -  France -  Métro Gaité
Phone: +33 (0) 1 43 35 00 37-   Fax: +33 (0) 1 43 35 00 76
mailto:elac...@easter-eggs.com  -   http://www.easter-eggs.com

Re: [rt-users] Scrip to enforce maximum ticket status per person per queue?

2016-01-15 Thread Emmanuel Lacour 
Le 13/01/2016 20:55, Aaron McCormack a écrit :
> Hi RT Users-
> 
> I'm looking to create a scrip which enforces a maximum number of tickets of a 
> certain status, per person, per queue.
> 
> For example:
> 
> Joe has 3 status open tickets and 4 status stalled tickets.  By policy, Joe 
> is only allowed to have 3 open tickets at once.
> 
> Joe tries to change 1 of the stalled tickets to open, but RT counts the 
> number of status open tickets that Joe already has and doesn't allow the 
> status change.  If Joe then changes 1 open ticket to resolved, then he can 
> change 1 stalled to open, maintaining his limit of 3 status open tickets.
> 
> Has anyone tried enforcing limitation like this or query the status of other 
> tickets in a scrip?
> 


I don't think you should use scrips for this because it will be asynchrone.

I would do:

- set a user or group CustomField to record each ones limits
- add a method to local/lib/RT/User_Local.pm named CheckStatusLimit,
that retrieve the user/group limit, get the list of owned tickets and
check if limit are reached, then return if the new status is allowed or not.
- use callbacks (Tickt/Display.html and other plaes where user can
change status) or override maybe ProcessTicketBasics, to use this method
before accepting status change. Display proper error to user if not allowed


I would avoid enforcing this in Ticket->SetStatus method as you may
wan't to allow others to force status or even scripts.



-- 
Easter-eggs  Spécialiste GNU/Linux
44-46 rue de l'Ouest  -  75014 Paris  -  France -  Métro Gaité
Phone: +33 (0) 1 43 35 00 37-   Fax: +33 (0) 1 43 35 00 76
mailto:elac...@easter-eggs.com  -   http://www.easter-eggs.com

[rt-users] "RT::Authen::ExternalAuth".

2016-01-15 Thread ggamache 
Question on "RT::Authen::ExternalAuth".
I've set the ExternalAuth and it worked
Is there a way to have both auth External and still be able to log with the
internal DB ? 

regards,
Ghis





--
View this message in context: 
http://requesttracker.8502.n7.nabble.com/RT-Authen-ExternalAuth-tp61193.html
Sent from the Request Tracker - User mailing list archive at Nabble.com.