unable to capture eppn information from SAML2/POST at SP

[Peter Schober]

* O'Quinn, Dennis <DENNIS_OQUINN at homedepot.com> [2018-06-12 00:14]:
> Thanks, but, not sure how to apply that guidance.  This is what the
> IdP is sending me.  Are you saying I can override that someway and
> 'change' it to eduPersonPrincipalName?

You're mapping the attribute from 'name="eppn"' to 'id="eppn"',
literally in the attribute-map.xml.
(The only way to make this more obvious -- other than the
documentation explaining that this is what happens -- would be calling
the parameters 'from' instead of 'name' and 'to' instead of 'id'.)

It's the latter (the 'id' you've chosen in your attribute-map.xml)
that triggers the SP's built in checks for the eduPersonPrincipalName
attribute, and that's what's reventing you from using it.

> BTW, Much of the documentation I am reading out there seems to imply
> that the configuration is being done by 'one' entity with access to
> "both" IdP and SP configurations and logs simultaneously.

No. But either way: I pointed out everything that was wrong with that
attribute as sent by the IDP (which was everything can can possibly be
wrong).
While you may not have the power to change it you're still free to
convince the IDP that what it does is wrong and not interoperable.
Assuming you're not the only SP in the world it's likely that the next
SP will then not have to go through your experience, once the IDP
fixes this.

-peter