Hi,
I've installed RT 4.0.8 on a RHEL 6.2 system and overall it's working
fine with one notable exception. We authenticate users with Shibboleth,
and once so authenticated they are able to create tickets. First time
users have their accounts auto-created. We had a previous instance of
RT 3
On Wed, Nov 21, 2012 at 01:24:11PM -0500, John Johnston wrote:
>I've installed RT 4.0.8 on a RHEL 6.2 system and overall it's working fine
> with one notable
>exception. We authenticate users with Shibboleth, and once so
> authenticated they are able to
>create tickets. First time u
Thanks Kevin,
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'};
my $your_full_name = $ENV{'displayName'};
my $your_phone = $query->param("PHONE");
my
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_US
Actually no, REMOTE_USER in our institution includes the domain name, so
in this example it would be jo...@msu.edu. 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:
On Tue, Nov 27, 2012 at 10:47:27PM -0500, John Johnston wrote:
>Actually no, REMOTE_USER in our institution includes the domain name, so
> in this example it
>would be jo...@msu.edu. I have double checked this by having the form
> spit out the
>variables returned by the Shibboleth Id
