yavor at nyu.edu
Wed Jul 31 09:57:33 EDT 2019
This is exactly what we did two weeks ago, but it didn't work. The LinkedIn
engineer said they need to work on the problem. My guess is, the value of
the entitlement was not handle properly, since it is -
On Wed, Jul 31, 2019 at 9:43 AM Cantor, Scott <cantor.2 at osu.edu> wrote:
> On 7/31/19, 9:22 AM, "Cantor, Scott" <cantor.2 at osu.edu> wrote:
> > I had no trouble with that. I did happen to only pass one value so
> perhaps that was/is broken. They have been updating
> > things, so I'll have to re-test in case they broke anything.
> Authz still works.
> Add custom attribute mapping for "urn:oid:220.127.116.11.4.1.5918.104.22.168.7", check
> "Add access rules", Select rule "Whitelist", set Allow If to the
> entitlement value you're using.
> -- Scott
> For Consortium Member technical support, see
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
Systems Developer for Identity Services
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the users