Issue with releasing eduPersonPrincipalName to Specific SP
Edward Patri
Edward.Patri at csi.cuny.edu
Wed Apr 26 18:20:54 EDT 2017
Hi All,
I changed the xsi:type to ad:Prescoped and it resolved the issue.
I confirmed with the end users that they are able to now log into the system using our IDP.
Thanks for all of your assistance on this matter.
Edward Patri
Networking Services
CUNY - College of Staten Island
2800 Victory Blvd 2A-300
Staten Island, NY 10314
Office: (718) 982-2705
Edward.Patri at csi.cuny.edu
-----Original Message-----
From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Cantor, Scott
Sent: Wednesday, April 26, 2017 6:18 PM
To: Shib Users <users at shibboleth.net>
Subject: Re: Issue with releasing eduPersonPrincipalName to Specific SP
On 4/26/17, 6:16 PM, "users on behalf of Brent Putman" <users-bounces at shibboleth.net on behalf of putmanb at georgetown.edu> wrote:
> Ok. But if the value returned from the data connector already is a
> scoped string, e.g. is "some.principal at example.edu", then wouldn't you
> use the Prescoped attribute definition, per my other note?
Probably, my actual knowledge of the resolver is limited to whatever I happen to go look up at any given time.
But I think we're being too silent in the logs if this stuff isn't very obvious. Applying a scoped encoder to a simple attribute should bark loudly.
-- Scott
--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
More information about the users
mailing list