Linkedin learning

[Paul B. Henson]

> From: mat houser
> Sent: Tuesday, July 30, 2019 12:24 PM
> 
> I'm curious if anybody has gotten linkedin learning SSO working properly
> with the Shibboleth IdP.

We recently migrated from lynda.com to linked in learning. Other than the already mentioned annoying backpedal from federated metadata to ad hoc metadata (they say it's "more secure"), and the caveat that encryption must be disabled it was fairly straightforward. I believe links to the documentation have already been posted; I did have some confusion as to whether not they wanted the "friendly name" for the attribute or the urn -based name, when I initially put the wrong one I did get the same error as you. As I recall I had to put the urn.

Also, another annoyance the documentation doesn't really discuss well; they really really really really really try to encourage new users to link their linked in learning account to their linkedin.com account. The latter intentionally does not support SSO (they say for security reasons 8-/, they don't want an employer to be able to hijack and employees linkedin.com account; who uses their work account for their primary linkedin.com access???). If the two accounts are linked, after you authenticate via SSO, you then need to provide your local linkedin.com username/password before you actually get in. This is very confusing for people who do SSO and then immediately see a username/password prompt :(.

--
Paul B. Henson  |  (909) 979-6361  |  http://www.cpp.edu/~henson/
Operating Systems and Network Analyst  |  henson at cpp.edu
California State Polytechnic University  |  Pomona CA 91768