[EXTERNAL] Re: unable to capture eppn information from SAML2/POST at SP

[O'Quinn, Dennis]

Well, until I know (and understand) all the moving parts better, any standard I come up with may well be 'broken' as far as the features and safety that a properly configured Shibboleth may offer...

After I dig a little more, I intend to go back to Peter for a better definition of 'broken' in my case, since, I don't even know enough yet to know *what* would be broken, much less where or how....


-----Original Message-----
From: users <users-bounces at shibboleth.net> On Behalf Of Alan Buxey
Sent: Wednesday, June 13, 2018 5:12 AM
To: Shib Users <users at shibboleth.net>
Subject: Re: [EXTERNAL] Re: unable to capture eppn information from SAML2/POST at SP

hi,

> Thank you sir...  was just trying to make it fit into the paradigm of the rest of the product.  I will come up with my own 'broken' standard and reconfigure...  Esp. since now (before going production) is certainly the time to do it...

please don't try to label it as a broken standard. you noted yourself that there appeared to be a lot of fore-knowledge required for some things and this is true of some attributes/names/methods. I would suggest you read up on ePPN if you want to use that (to eg copy examples/docs) - there's a whole body looking after that namespace/usage (same for schac* too).  you can use plenty of other standard, documented SAML attributes :)

alan
--
For Consortium Member technical support, see https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.shibboleth.net_confluence_x_coFAAg&d=DwICAg&c=MtgQEAMQGqekjTjiAhkudQ&r=mn6DeBt1nj8Oqx06pdIK0_n5EfK6FeVHgdjBNpchyro&m=hVrKX1zkarhtyGaNs2qHYEGiHUKb1ulTeX9Vx8-HqNc&s=5CjIKUT2RgNRLpMf4tZn-FDEVfdYb4HY_7nF1bNAp5o&e=
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net