Hi, I think it's the best strategy : focus our efforts on 4.0. About the release date, hard to say. 4.0 is a big change and some things have been broken. I see 12 JIRA tickets still open for 4.0. I will try to address them this week... A RC2 before the end of september would be great. Best regards, Jérôme
2013/9/10 Robert von Bismarck <rvonb...@gmail.com> > Hi, > > Ok, definitely broken then. I certainly prefer going forward with CAS 4.0 > which should be more future-proof and migrate the remainder of our services > onto that. Do you have any idea how far the release date is ? > > BTW: I really like the size of the CAS webapp now, it went from 38M in > 3.x.x to 22M in 4.0.0 with added functionality, that is quite cool :-) > > Kind regards, > > Robert > > > > On 10 September 2013 17:43, Jérôme LELEU <lel...@gmail.com> wrote: > >> Hi, >> >> You can find this information in the wiki : >> https://wiki.jasig.org/display/CASUM/Configuration+for+the+OAuth+client+support+in+CAS+server+version+%3E%3D+3.5.1 >> . >> In that case, it's LinkedInProviderUrl. >> That said, it won't work as LinkedIn changed the response they send and >> CAS server 3.5.2 is based on an old version of the scribe-up library >> (1.2.0). I remember having this discussion with someone but it didn't go >> any further. >> What is necessary here if you want to use CAS 3.5.2 with LinkedIn is to >> exclude scribe-up 1.2.0 to explicitely depend on scribe-up 1.3.2-SNAPSHOT >> on which I need to patch the LinkedIn support (before I release it). >> >> Can you confirm that you need the LinkedIn support ? >> >> Thanks. >> Best regards, >> Jérôme >> >> >> >> >> 2013/9/10 Robert von Bismarck <rvonb...@gmail.com> >> >>> Hello, >>> >>> Finally had some time to get back to this. >>> >>> I had a go with 4.0.0-RC2 and had the same issue at first, but quickly >>> found that I had a typo in the variable used as href target in * >>> casLoginView.jsp* >>> <a href="${LinkedIn2ClientUrl}">Authenticate with LinkedIn</a> >>> I corrected my typo and it worked, which was kinda cool. But my boss >>> does not want to see a pre-release with bleeding edge code in production, >>> which I perfectly underestand. >>> So, I went back to 3.5.2 and tried my luck again, by changing the >>> variable name but no luck there. I would very much like to backtrace the >>> code, but my jsp-Fu is not strong enough to find out how the variable is >>> really named in the code and where it gets instantiated. >>> >>> Any help welcome, >>> >>> Robert >>> >>> >>> >>> On 27 August 2013 14:09, Jérôme LELEU <lel...@gmail.com> wrote: >>> >>>> Hi, >>>> >>>> The *OAuth10LoginController* just needs to be defined in the * >>>> cas-servlet.xml*. The appropriate url (direct to the provider or to >>>> this controller) is computed internally in the *OAuthAction* class. >>>> Note that this is no more necessary with CAS server 4.0. >>>> Best regards, >>>> Jérôme >>>> >>>> >>>> >>>> 2013/8/27 Robert von Bismarck <rvonb...@gmail.com> >>>> >>>>> Hi, >>>>> >>>>> >>>>> Thanks for the follow-up, I'm actually using 1.2.0 of scribe-up as per >>>>> the wiki, I will redeploy the instances using 1.3.1 and see if that >>>>> works better, I will also up the loglevel for scribe-up in log4j >>>>> config. >>>>> >>>>> As for the link, should I reference the oauth10logincontroller >>>>> somewhere in the applicationContext.xml, like in LoginUrl ? >>>>> >>>>> Currently I have : >>>>> >>>>> <bean id="oauthConfig" >>>>> class="org.jasig.cas.support.oauth.OAuthConfiguration"> >>>>> <property name="loginUrl" value="https://cas.test/cas/login"; /> >>>>> <property name="providers"> >>>>> <list> >>>>> <ref bean="linkedin" /> >>>>> </list> >>>>> </property> >>>>> </bean> >>>>> >>>>> Cheers, >>>>> >>>>> Robert >>>>> >>>>> On 27 August 2013 11:02, Jérôme LELEU <lel...@gmail.com> wrote: >>>>> > Hi, >>>>> > >>>>> > You're right about the behaviour : the link to "Authenticate at >>>>> LinkedIn" is >>>>> > not directly pointed to LinkedIn, it's an internal link which >>>>> requires the >>>>> > oauth10logincontroller. And also about the typo : I just fixed the >>>>> wiki. >>>>> > >>>>> > There is a problem with the LinkedIn support. I'm not sure if I >>>>> fixed it in >>>>> > scribe-up 1.3.1 (CAS server uses scribe-up 1.2.0). If no, I think I >>>>> can >>>>> > figure something out for that, maybe a 1.3.2 version ? >>>>> > At least, it's fixed for the new version 4.0 of the CAS server. >>>>> > >>>>> > Best regards, >>>>> > Jérôme >>>>> > >>>>> > >>>>> > >>>>> > 2013/8/26 Robert von Bismarck <rvonb...@gmail.com> >>>>> >> >>>>> >> Hi list, >>>>> >> >>>>> >> I am currently trying to include linkedin via OAuth in my CAS setup. >>>>> >> >>>>> >> I followed the doc at >>>>> >> >>>>> >> >>>>> https://wiki.jasig.org/display/CASUM/Configuration+for+the+OAuth+client+support+in+CAS+server+version+%3E%3D+3.5.1 >>>>> >> and I get an empty "Authenticate with Linkedin" URL in my login >>>>> page. >>>>> >> >>>>> >> As I'm not really a Java EE hacker, from the docs and code, I assume >>>>> >> that this link gets auto-generated to request a token from LinkedIn >>>>> >> using the secret and key we got from LinkedIn in >>>>> >> ApplicationContext.xml, right ? >>>>> >> >>>>> >> Secondly, from the code, I made the assumption that LinkedIn is >>>>> >> automagically setup as OAuth 1.0 and it will require the >>>>> >> oauth10logincontroller in cas-servlet.xml. >>>>> >> >>>>> >> During config I had to change one thing in the linkedin provider >>>>> bean >>>>> >> (probably a typo in the CAS wiki) >>>>> >> >>>>> >> <bean id="linkedin" class="org.scribe.up.impl.LinkedInProvider"> >>>>> >> >>>>> >> To : >>>>> >> >>>>> >> <bean id="linkedin" >>>>> class="org.scribe.up.provider.impl.LinkedInProvider"> >>>>> >> >>>>> >> >>>>> >> Details of the setup : >>>>> >> >>>>> >> - CAS 3.5.2 as maven overlay >>>>> >> - scribe-up 1.2.0 as per the docs >>>>> >> - Tomcat 7.0.42 container >>>>> >> - Authenticationprovider is LDAP and works fine >>>>> >> - inmemory service registry for testing, but I will probably use >>>>> JSON >>>>> >> service registry for production >>>>> >> - ehcache ticket registry shared between cluster nodes >>>>> >> - apache mod_proxy_ajp load-balancer on one node for testing, will >>>>> use >>>>> >> hardware load-balancer for SSL offloading in production >>>>> >> >>>>> >> Thanks for any hints as currently I'm a bit lost how to debug this. >>>>> >> >>>>> >> Robert >>>>> >> >>>>> >> -- >>>>> >> You are currently subscribed to cas-user@lists.jasig.org as: >>>>> >> lel...@gmail.com >>>>> >> To unsubscribe, change settings or access archives, see >>>>> >> http://www.ja-sig.org/wiki/display/JSG/cas-user >>>>> > >>>>> > >>>>> > -- >>>>> > You are currently subscribed to cas-user@lists.jasig.org as: >>>>> > rvonb...@gmail.com >>>>> > To unsubscribe, change settings or access archives, see >>>>> > http://www.ja-sig.org/wiki/display/JSG/cas-user >>>>> >>>>> -- >>>>> You are currently subscribed to cas-user@lists.jasig.org as: >>>>> lel...@gmail.com >>>>> To unsubscribe, change settings or access archives, see >>>>> http://www.ja-sig.org/wiki/display/JSG/cas-user >>>>> >>>>> >>>> -- >>>> You are currently subscribed to cas-user@lists.jasig.org as: >>>> rvonb...@gmail.com >>>> To unsubscribe, change settings or access archives, see >>>> http://www.ja-sig.org/wiki/display/JSG/cas-user >>>> >>>> >>> -- >>> You are currently subscribed to cas-user@lists.jasig.org as: >>> lel...@gmail.com >>> To unsubscribe, change settings or access archives, see >>> http://www.ja-sig.org/wiki/display/JSG/cas-user >>> >>> >> -- >> You are currently subscribed to cas-user@lists.jasig.org as: >> rvonb...@gmail.com >> To unsubscribe, change settings or access archives, see >> http://www.ja-sig.org/wiki/display/JSG/cas-user >> >> > -- > You are currently subscribed to cas-user@lists.jasig.org as: lel...@gmail.com > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > > -- You are currently subscribed to cas-user@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
