Re: [rt-users] How do I set the RT hostname?

[Peter Zillmann]

On my test system I get the behavior you describe when $WebDomain does not 
match the URL in my browser.

Are you sure you’ve restarted your web server since making the change?

From: rt-users [mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of 
Barton Chittenden
Sent: Monday, November 21, 2016 8:19 AM
To: rt-users
Subject: [rt-users] How do I set the RT hostname?

I'm in the process of setting up a new RT 4.4 instance. I used the web 
installer, which generated the following RT-SiteConfig.pm:

Set( $CommentAddress, 'd...@example.com' );
Set( $CorrespondAddress, 'd...@example.com' );
Set( $DatabaseHost, 'localhost' );
Set( $DatabaseName, 'rt4' );
Set( $DatabasePassword, 'x' );
Set( $DatabasePort, '' );
Set( $DatabaseType, 'mysql' );
Set( $DatabaseUser, 'rt_user' );
Set( $Organization, 'rt2.example.com' );
Set( $OwnerEmail, 'd...@example.com' );
Set( $SendmailPath, '/usr/sbin/sendmail' );
Set( $WebDomain, 'rt2.example.com' );
Set( $WebPort, '80' );
Set( $rtname, 'rt2.example.com' );
1;

{ I've substituted 'rt2.example.com' for the actual 
FQDN of the machine that's hosting the instance }

When I tried to set up a new asset, I got the following error message:

RT has detected a possible cross-site request forgery for this request, because 
the Referrer header supplied by your browser 
(rt2.example.com:80) is not allowed by RT's 
configured hostname (127.0.0.1:80).

A bit of googling showed me how to set this in  RT-SiteConfig.pm:

Set(@ReferrerWhitelist, qw(127.0.0.1:80));

... that did disable the message, but why is the 'configured hostname' set to 
127.0.0.1:80, and how do I set it to the actual domain 
name of the machine?

Thanks,

--Barton


-
RT 4.4 and RTIR training sessions, and a new workshop day! 
https://bestpractical.com/training
* Los Angeles - January 9-11 2017

[rt-users] creativity and expertise with Assets and lifecycles

[Peter Zillmann]

Greetings!

I've set up Assets on a test server for our staff to evaluate. They like it 
very much so far, but they've got one need I haven't yet figured out how to 
meet with Assets. I feel like I've read through documentation, wiki, and mail 
archives, and I don't think I've found my answer.

Our staff want to use Assets to track who has a shareable resource. The 
resource might be in inventory, or checked out to a patron. The workflow they 
want needs to be linear, and ideally a single-screen process. They'll want to 
change "held-by" for a resource, and change the item's lifecycle status (from 
on-shelf to checked-out).

I think we're only going to be able to make this workflow work for them if we 
can use a Scrip with a custom action. Existing documentation regarding this 
seems to be written all from a Tickets perspective, leaving me feeling a bit at 
sea.

So, am I wrong to think Assets might be able to meet our need? Or am I thinking 
of this the wrong way? I thought of trying to use a Comment or Respond action 
on an asset, but those features don't seem to exist (I've tried configuring 
them like tickets, but they don't seem to work). Would I be smarter to create a 
linked ticket for each "check-out"/"check-in"?

Would anyone be able to point me in the right direction?

Thanks much,
Peter

--
Peter Zillmann
Systems & Networking Associate
Information Services
Kalamazoo College
1200 Academy Street
Kalamazoo, MI, 49006
269.337.5800
peter.zillm...@kzoo.edu