Actually no, REMOTE_USER in our institution includes the domain name, so
in this example it would be [email protected]. I have double checked this
by having the form spit out the variables returned by the Shibboleth IdP.
John
On 11/27/12 10:07 PM, Kevin Falcone wrote:
On Tue, Nov 27, 2012 at 01:30:41PM -0500, John Johnston wrote:
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'};
Presumably REMOTE_USER is set to johnj rather than [email protected]?
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;
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
--------
We're hiring! http://bestpractical.com/jobs
--------
We're hiring! http://bestpractical.com/jobs
