Hi Chris, so CAS redirects to http://otrs/customer.pl (without params)? If it's so, you need to change CAS to keep the requested params to do the correct redirect. :-) Many greetings, -Martin Chris schrieb:

Martin,

your scenario is correct ..... just one little problem.

CAS needs a serviceURL and that is http://otrs/customer.pl I cant use the request url with the parameters. When cas returns it will ask for this url and I have lost my parameters. I am not a Perl guy and have no idea how to hang on to the original requestURL. Could we but it in the session somehow ?

Any ideas on how to accomplish this ?

Thanks Chris

-----Original Message-----

...

From: Martin Edenhofer Sent: May 11, 2007 9:00 AM To: Chris Subject: Re: [dev] HTTPBasicAuth and CustomerMessage

Hi Chris,

Chris schrieb:

...

I use CAS for SSO for all my applications including OTRS. I log in through my portal and then I navigate from there to different application.

We want to be able to automatically create trouble tickets in otrs when an operator encounters an error in an application.On some application screens we have a link to otrs example : http:://server/otrs/customer.pl?Action=CustomerMessage.pl&....) where we attach the error number to the URL. We then fill in the body and subject of the OTRS ticket automatically with this error number.

Here is the problem, the first time we call this URL we get redirected to the customer.pl screen IF THE USER has not visited /otrs/customer.pl. When I call the url again it redirects us to the right place and we fill in the errorcode automaticaly.

The first time we make the call to OTRS HTTPBasicAuth redirects me to the CAS server where the CAS ticket/cookie is created for the OTRS service and returns the user. I think at this point OTRS automatically assumes that the user is loging on and redirects the user to customer.pl, but we would like to goto directly to customer.pl?Action=CustomerMessage.pl..

Is there a way to accomplish this ?

Hope this makes sense ? Now I think I got it a little bit more. ;)

It depends on the URLs. For example:

1) URL to OTRS http://host/otrs/customer.pl?Action=CustomerMessage.pl&...

2) OTRS redirect to CAS

http://cas/someurl.xxx?RequestedURL=http://host/otrs/customer.pl?Action=Cust......

3) Redirect from CAS back to OTRS with ticket/cookie (so this URL is not clear to me (where is the ticket/cookie) but could look like this)

http://host/otrs/customer.pl?Action=CustomerMessage.pl&...&CAS=1234...

Then it should work fine (go directly to the create ticket screen). But I think point 3 is a little bit different. Isn't it? :)

...

Thanks Chris -Martin

((otrs)) :: OTRS GmbH :: Europaring 4 :: D - 94315 Straubing Fon: +49 (0) 9421 56818 0 :: Fax: +49 (0) 9421 56818 18 http://www.otrs.com/ :: Communication with success!