<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>
<div>Thank you for the quick response. I had a typo in the relyingPartyIds value. Everything is working great now.</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:12pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>users <<a href="mailto:users-bounces@shibboleth.net">users-bounces@shibboleth.net</a>> on behalf of "Cantor, Scott" <<a href="mailto:cantor.2@osu.edu">cantor.2@osu.edu</a>><br>
<span style="font-weight:bold">Reply-To: </span>Shib Users <<a href="mailto:users@shibboleth.net">users@shibboleth.net</a>><br>
<span style="font-weight:bold">Date: </span>Wednesday, October 28, 2015 at 10:42 AM<br>
<span style="font-weight:bold">To: </span>Shib Users <<a href="mailto:users@shibboleth.net">users@shibboleth.net</a>><br>
<span style="font-weight:bold">Subject: </span>Re: Google Apps - Invalid Email<br>
</div>
<div><br>
</div>
<div>
<div>
<div>On 10/28/15, 1:28 PM, "users on behalf of Muzinich, Mike" <<a href="mailto:users-bounces@shibboleth.net">users-bounces@shibboleth.net</a> on behalf of
<a href="mailto:MuziniM@losrios.edu">MuziniM@losrios.edu</a>> wrote:</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>I am sure I am missing something simple but I am having a problem with Google not recognizing the email address attribute I am setting and releasing.</div>
</blockquote>
<div><br>
</div>
<div>Google doesn't use attributes. It's a broken service in a number of regards and relies on the NameID.</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div> This is for the upgrade to IDP 3.1.2. I did not retain the existing Shibboleth configuration, I modified the native 3.1.2 config files.</div>
</blockquote>
<div><br>
</div>
<div>You are however still using the legacy NameID generation approach using the resolver.</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div> The correct email address shows up when I am prompted by Shibb to share the information with Google</div>
</blockquote>
<div><br>
</div>
<div>Those are attributes. The release page doesn't know anything about NameIDs. Unfortunate limitation that would probably get addressed down the road if we see actual evidence people are using the consent code much at all.</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>and there are no errors in the logs. It also tests successfully with TestShib. This is the applicable attribute resolver and filter configurations.</div>
</blockquote>
<div><br>
</div>
<div>You can't make this work without forcing the NameID format selection process to choose the "unspecified" format, and the only way to do that is via a relying party override and the nameIDFormatPrecedence property.</div>
<div><br>
</div>
<div>Or you can use the new docs on custom NameID generation and follow those, but you'll still have to force the format selection in the same way.</div>
<div><br>
</div>
<div>-- Scott</div>
<div><br>
</div>
<div>-- </div>
<div>To unsubscribe from this list send an email to <a href="mailto:users-unsubscribe@shibboleth.net">
users-unsubscribe@shibboleth.net</a></div>
<div><br>
</div>
</div>
</div>
</span>
</body>
</html>