<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Actually no, REMOTE_USER in our
institution includes the domain name, so in this example it would
be <a class="moz-txt-link-abbreviated" href="mailto:johnj@msu.edu">johnj@msu.edu</a>. I have double checked this by having the form
spit out the variables returned by the Shibboleth IdP.<br>
<br>
John<br>
<br>
On 11/27/12 10:07 PM, Kevin Falcone wrote:<br>
</div>
<blockquote cite="mid:20121128030744.GI1823@jibsheet.com"
type="cite">
<pre wrap="">On Tue, Nov 27, 2012 at 01:30:41PM -0500, John Johnston wrote:
</pre>
<blockquote type="cite">
<pre wrap=""> We've been using the REST API for creating the tickets. We assign certain critical variables
using the values returned by Shibboleth authentication first:
my $your_netid = $ENV{'REMOTE_USER'};
</pre>
</blockquote>
<pre wrap="">
Presumably REMOTE_USER is set to johnj rather than <a class="moz-txt-link-abbreviated" href="mailto:johnj@msu.edu">johnj@msu.edu</a>?
</pre>
<blockquote type="cite">
<pre wrap=""> my $ticket = RT::Client::REST::Ticket->new(
rt => $rt,
queue => "General",
subject => "$your_subject",
requestor => [$your_netid],
cf => {
'public' => $your_public,
},
)->store(text => "$your_comments");
my $newticket = $ticket->id;
</pre>
</blockquote>
<pre wrap="">
With this call, I don't see how RT could possibly know your Email
Address. My assumption is that your RT 3.0 install had a local
modification to set empty Email Addresses to the Username +
@yourdomain. This is a pretty common thing to do using the
CanonicalizeUserInfo method. I'd suggest checking for a missed
customization.
-kevin
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">--------
We're hiring! <a class="moz-txt-link-freetext" href="http://bestpractical.com/jobs">http://bestpractical.com/jobs</a>
</pre>
</blockquote>
<br>
</body>
</html>