
Hi! Is there any way to implement such configuration scenario? 1) Help desk employees and technicians can access OTRS from our Remote Desktop Server only (it can be a source IP address check) 2) Customers can access from anywhere I believe this could be achieved in two ways: 1) In user configuration, set IP address restriction (better, IMHO). If the configuration is empty, then it can Access from anywhere. 2) Customizing the code for each restricted page (which ones?), except pages customer would have access to. Has anyone tried anything similar? Any tips on how to achieve that? Thanks, -- Atenciosamente, Edson Carlos Ericksson Richter

We are using 2 step authentification - Google Auth and https and allow acces from outside too. Regards, Raul
On 24 Nov 2015, at 19:32, Edson Richter
wrote: 1) Help desk employees and technicians can access OTRS from our Remote Desktop Server only (it can be a source IP address check)

Sorry, I could not understand how Google Auth would help me limit the user IP address access to the OTRS system. Would you ellaborate a bit more? I tend to prefer a in house solution without external APIs, but is just a matter of understanding how Google Auth can help. Thanks, Atenciosamente, Edson Carlos Ericksson Richter Em 24/11/2015 15:36, Raul Orav escreveu:
We are using 2 step authentification - Google Auth and https and allow acces from outside too.
Regards, Raul
On 24 Nov 2015, at 19:32, Edson Richter
mailto:edsonrichter@hotmail.com> wrote: 1) Help desk employees and technicians can access OTRS from our Remote Desktop Server only (it can be a source IP address check)
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs

Basically if you do some 2 step authentification then apache doesn’t allow to connect without password. Depends which auth do you use. But if you are up to date then it’s a good solution how to keep your OTRS public and secure. But I think your solution could be in configuring apache allow directives.
On 24 Nov 2015, at 19:49, Edson Richter
wrote: Sorry, I could not understand how Google Auth would help me limit the user IP address access to the OTRS system. Would you ellaborate a bit more? I tend to prefer a in house solution without external APIs, but is just a matter of understanding how Google Auth can help.
Thanks, Atenciosamente,
Edson Carlos Ericksson Richter Em 24/11/2015 15:36, Raul Orav escreveu:
We are using 2 step authentification - Google Auth and https and allow acces from outside too.
Regards, Raul
On 24 Nov 2015, at 19:32, Edson Richter < mailto:edsonrichter@hotmail.comedsonrichter@hotmail.com mailto:edsonrichter@hotmail.com> wrote:
1) Help desk employees and technicians can access OTRS from our Remote Desktop Server only (it can be a source IP address check)
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs http://lists.otrs.org/cgi-bin/listinfo/otrs
OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs

You can use apache location ip limit.
https://httpd.apache.org/docs/2.2/howto/access.html
On Tue, Nov 24, 2015 at 11:32 AM, Edson Richter
Hi!
Is there any way to implement such configuration scenario?
1) Help desk employees and technicians can access OTRS from our Remote Desktop Server only (it can be a source IP address check) 2) Customers can access from anywhere
I believe this could be achieved in two ways:
1) In user configuration, set IP address restriction (better, IMHO). If the configuration is empty, then it can Access from anywhere. 2) Customizing the code for each restricted page (which ones?), except pages customer would have access to.
Has anyone tried anything similar? Any tips on how to achieve that?
Thanks,
-- Atenciosamente,
Edson Carlos Ericksson Richter
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
--
*Diego Chacón Rojas*
** E-mail: diego@gridshield.net

You could create two vhosts in apache, one for customers and one for
agents. Lock the agent vhost down to access only from the rdp server
On 24 Nov 2015 17:58, "Diego Chacón"
You can use apache location ip limit. https://httpd.apache.org/docs/2.2/howto/access.html
On Tue, Nov 24, 2015 at 11:32 AM, Edson Richter
wrote: Hi!
Is there any way to implement such configuration scenario?
1) Help desk employees and technicians can access OTRS from our Remote Desktop Server only (it can be a source IP address check) 2) Customers can access from anywhere
I believe this could be achieved in two ways:
1) In user configuration, set IP address restriction (better, IMHO). If the configuration is empty, then it can Access from anywhere. 2) Customizing the code for each restricted page (which ones?), except pages customer would have access to.
Has anyone tried anything similar? Any tips on how to achieve that?
Thanks,
-- Atenciosamente,
Edson Carlos Ericksson Richter
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
-- *Diego Chacón Rojas* ** E-mail: diego@gridshield.net
* --------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs

Hi, John. This seems exactly what I'm looking for. Thanks, I'll investigate a bit more. Kind regards, Atenciosamente, Edson Carlos Ericksson Richter Em 24/11/2015 16:08, John O'Neill escreveu:
You could create two vhosts in apache, one for customers and one for agents. Lock the agent vhost down to access only from the rdp server
On 24 Nov 2015 17:58, "Diego Chacón"
mailto:diego@gridshield.net> wrote: You can use apache location ip limit. https://httpd.apache.org/docs/2.2/howto/access.html
On Tue, Nov 24, 2015 at 11:32 AM, Edson Richter
mailto:edsonrichter@hotmail.com> wrote: Hi!
Is there any way to implement such configuration scenario?
1) Help desk employees and technicians can access OTRS from our Remote Desktop Server only (it can be a source IP address check) 2) Customers can access from anywhere
I believe this could be achieved in two ways:
1) In user configuration, set IP address restriction (better, IMHO). If the configuration is empty, then it can Access from anywhere. 2) Customizing the code for each restricted page (which ones?), except pages customer would have access to.
Has anyone tried anything similar? Any tips on how to achieve that?
Thanks,
-- Atenciosamente,
Edson Carlos Ericksson Richter
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
-- /Diego Chacón Rojas/ /* E-mail: diego@gridshield.net mailto:diego@gridshield.net/ //
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
participants (4)
-
Diego Chacón
-
Edson Richter
-
John O'Neill
-
Raul Orav