Re: [rt-users] Autoreply Template Script

2015-02-03 Thread Christian Loos
Am 03.02.2015 um 10:57 schrieb Vas: So none of provide a web interface to view the status of there tickets? If yes how do you do it? Because from the user side If I send requests on a regular basis and decided to see the status of them I would not remember the username and password that was

Re: [rt-users] Autoreply Template Script

2015-02-03 Thread Iain Rae
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/02/15 11:02, Sam Wilson wrote: As with Nathan, we use Shibboleth SP and apache to authenticate users via our internal SSO connected to LDAP. This will provision their accounts as well as provide them with up to date passwords. It sounds

Re: [rt-users] Autoreply Template Script

2015-02-03 Thread Vas
Thank you Alex for the reply. Do you think there is a way to make it instead to create an initial password for every ticket it receives? Regardless if the sender has send a request before? Thank you Vas -- View this message in context:

Re: [rt-users] Autoreply Template Script

2015-02-03 Thread Sam Wilson
As with Nathan, we use Shibboleth SP and apache to authenticate users via our internal SSO connected to LDAP. This will provision their accounts as well as provide them with up to date passwords. It sounds like external auth might be an option worth considering. Sam. On Tue, Feb 3, 2015 at 8:15

Re: [rt-users] Autoreply Template Script

2015-02-03 Thread Nathan Cutler
So none of provide a web interface to view the status of there tickets? If yes how do you do it? We do provide our users access to the self-service web UI. We have the usernames and passwords in LDAP, and RT uses RT::Authen::ExternalAuth for authentication. Of course, the users must remember

Re: [rt-users] Autoreply Template Script

2015-02-03 Thread Alex Peters
I believe that what you're asking is not possible. RT doesn't store passwords, and so it can't retrieve previous passwords for display in an email. It can only display the initial password because it manages the creation of that initial password, and therefore can take a copy. On 3 Feb 2015 8:30

Re: [rt-users] Autoreply Template Script

2015-02-03 Thread Vas
So none of provide a web interface to view the status of there tickets? If yes how do you do it? Because from the user side If I send requests on a regular basis and decided to see the status of them I would not remember the username and password that was generated on my first ever request which

Re: [rt-users] Autoreply Template Script

2015-02-03 Thread Vas
Has anyone else come across this ? Thank you Vas -- View this message in context: http://requesttracker.8502.n7.nabble.com/Autoreply-Template-Script-tp59459p59505.html Sent from the Request Tracker - User mailing list archive at Nabble.com.

Re: [rt-users] Autoreply Template Script

2015-02-03 Thread Sam Wilson
And in the process reset user passwords on every ticket? That sounds wrong too On 3 Feb 2015, at 19:39, Vas vk...@cam.ac.uk wrote: Thank you Alex for the reply. Do you think there is a way to make it instead to create an initial password for every ticket it receives? Regardless if the

[rt-users] Autoreply Template Script

2015-01-28 Thread Vas
Hi all, this bellow is our autoreply template. Subject: AutoReply: {$Ticket-Subject} Greetings, This message has been automatically generated in response to the creation of a request for IT Support regarding: {$Ticket-Subject()}, a summary of which appears below. There is no need to