Hi, Are you using CAS server version 3.5.2 or 4.0.0 ?
If you use CAS server version 3.5.2, you only have the LinkedIn version 1.0 OAuth protocol support. And there are not many returned attributes. If you want more attributes, you should use the CAS server 4.0.0 which has a LinkedIn2Client : https://github.com/leleuj/pac4j/blob/1.4.x/pac4j-oauth/src/main/java/org/pac4j/oauth/client/LinkedIn2Client.java for which you can require more attributes. Best regards, Jérôme 2013/11/21 Richard Everett <[email protected]> > Hi Jerome, > > > > Yes, I am – sorry for not making that clear in my question. > > > > Regards, > > > > Richard > > > > *From:* Jérôme LELEU [mailto:[email protected]] > *Sent:* 21 November 2013 16:50 > *To:* [email protected] > *Subject:* Re: [cas-user] Correctly configuring CAS to return LinkedIn > attributes > > > > Hi, > > > > Are you talking about the OAuth support on the CAS server side ? > > Thanks. > > Best regards, > > Jérôme > > > > > > 2013/11/21 Richard Everett <[email protected]> > > All, > > > > We are using the .NET CAS client with CAS to allow our users to > authenticate with their LinkedIn credentials. If they opt to do so, we will > capture various parts of their profile (with their permission). > > > > The LinkedIn app has been set up to request that user’s full profile… > > > > > > And in *deployerConfigContext.xml* we have (we believe) set the relevant > settings for the relevant bean. > > > > <bean class="org.jasig.cas.services.RegexRegisteredService"> > > <property name="id" value="0" /> > > <property name="name" value="HTTP and HTTPS" /> > > <property name="description" value="Allows HTTP(S) protocols from > anywhere" /> > > <property name="serviceId" value="^(https?|http?)://.*" /> > > <property name="evaluationOrder" value="10000001" /> > > <property name="allowedAttributes"> > > <list> > > <!-- linkedIn --> > > <value>id</value> > > <value>first-name</value> > > <value>last-name</value> > > <value>maiden-name</value> > > <value>formatted-name</value> > > <value>location</value> > > <value>email-address</value> > > <value>headline</value> > > <value>industry</value> > > <value>num-connections</value> > > <value>picture-url</value> > > <value>publications</value> > > <value>languages</value> > > <value>skills</value> > > <value>educations</value> > > <value>num-recommenders</value> > > <value>recommendations-received</value> > > <value>following</value> > > <value>mfeed-rss-url</value> > > <value>job-bookmarks</value> > > <value>suggestions</value> > > <value>date-of-birth</value> > > <value>member-url-resources</value> > > <value>related-profile-views</value> > > <value>phone-numbers</value> > > <value>bound-account-types</value> > > <value>im-accounts</value> > > <value>main-address</value> > > <value>twitter-accounts</value> > > <value>connections</value> > > </list> > > </property> > > </bean> > > > > However, we are only getting a small set of attributes (headline, summary, > site-standard-profile-request, public-profile-url, location, positions, > formatted-name, first-name, num-connections, last-name, industry, > picture-url, access_token) passed to us. > > > > What additional configuration do we need to put in place in order to get > all of the attributes we are trying to get? > > > > Kind regards, > > > > RIchard > > -- > You are currently subscribed to [email protected] as: [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > > > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > > -- > You are currently subscribed to [email protected] as: [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
<<image001.png>>
