Great! Thanks. Regarding the url of the documentation, I would have the version in the url like: http://jasig.github.io/cas/4.0.0/index.html http://jasig.github.io/cas/4.1.0-SNAPSHOT/index.html<http://jasig.github.io/cas/4.0.0/index.html>
And I would make the "current" url: http://jasig.github.io/cas/current/index.html<http://jasig.github.io/cas/4.0.0/index.html> redirect to the latest stable release: http://jasig.github.io/cas/4.0.0/index.html. Best regards, Jérôme 2014-05-13 12:03 GMT+02:00 Misagh Moayyed <mmoay...@unicon.net>: > Few updates: > > > > The 4.0 documentation is now available here, inclusive of javadocs: > > http://jasig.github.io/cas/4.0.0/index.html > > > > I updated the release process as well with what I had to do in order to > get the docs working for a new version. I think we may want to reserve > “current” for master development and have the mater index page point to > 4.0.0? Or shall we create a new folder for documentation during development > of the next version? > > > > Furthermore, the cas protocol is also updated: > > http://www.jasig.org/node/395 > > > > However, I seem to have trouble to get http://www.jasig.org/cas/protocolto > work. Seems like the site does not pick up the changes I published and > still points to the old doc. Formatting of the code snippets and xml blobs > also needs a bit of work still. > > > > I’ll resume work again in a few hours. > > > > *From:* Jérôme LELEU [mailto:lel...@gmail.com] > *Sent:* Wednesday, May 07, 2014 11:51 AM > *To:* cas-dev@lists.jasig.org > *Subject:* Re: [cas-dev] [cas-user] Schedule for CAS 4.0 > > > > Hi, > > > > I finally finished the release. I encountered some troubles: slow or > stopped process, but it might be my computer... > > At least, I noticed the the check on NOTICE files is not disabled during > the release. I created a JIRA to fix that for the next release: > https://issues.jasig.org/browse/CAS-1450. > > > > The master has been upgraded to version 4.1.0-SNAPSHOT and I created a > 4.0.x branch (which is now at version 4.0.1-SNAPSHOT). > > > > I ran out of time to finish the release process and will perform the "Post > Release" tasks on Monday (I have a few days off). > > > > I will send an official announcement in a few minutes. > > > > Best regards, > > Jérôme > > > > > > 2014-05-07 9:06 GMT+02:00 Jérôme LELEU <lel...@gmail.com>: > > Hi, > > > > I'm about to merge: https://github.com/Jasig/cas/pull/430 and start the > release of CAS server 4.0.0. > > > > Raise your hand if you have any concern / problem... > > > > Best regards, > > Jérôme > > > > > > 2014-05-05 19:13 GMT+02:00 Misagh Moayyed <mmoay...@unicon.net>: > > Thanks. Just wanted to make sure that oauthwrapper components can still be > used in CAS4 for enabling Oauth server support. > > > > I am revising the documentation a bit and fixing a few formatting issues. > I’ll post back when things are near done so you can review and make > adjustments. > > > > *From:* Jérôme LELEU [mailto:lel...@gmail.com] > *Sent:* Monday, May 05, 2014 10:06 AM > *To:* cas-dev@lists.jasig.org > *Subject:* Re: [cas-dev] [cas-user] Schedule for CAS 4.0 > > > > Hi, > > > > Yes, indeed, pac4j is only meant to be used as a client for different > protocols (OAuth, OpenID, CAS...) and everything should be explained > properly in "Delegate authentication" (from the client side point of view): > http://jasig.github.io/cas/current/integration/Delegate-Authentication.html > . > > Though, the OAuth server support remains and can still be used reading the > "OAuth protocol" documentation: > http://jasig.github.io/cas/current/protocol/OAuth-Protocol.html. > > > > It might not be clear enough, but I didn't find any better documentation > organization. > > Just let me know if you have a better idea... > > > > Best regards, > > Jérôme > > > > > > 2014-05-05 18:45 GMT+02:00 Misagh Moayyed <mmoay...@unicon.net>: > > Jérôme, > > I am reviewing the documentation for OAuth/OpenID and pac4j on the > existing wiki, and all references seem to indicate that CAS with pac4j will > act as an Oauth client only. Is that correct? Is the ability to have CAS > behave like an Oauth provider dropped, or do we have docs that explain what > needs to be done for CAS4? > > > > Misagh > > > > *From:* Jérôme LELEU [mailto:lel...@gmail.com] > *Sent:* Monday, May 05, 2014 8:19 AM > *To:* cas-dev@lists.jasig.org > *Subject:* Re: [cas-dev] [cas-user] Schedule for CAS 4.0 > > > > Hi, > > > > I've struggled hard to find a fix. > > > > As I used Memcached locally, the setup was not easy and I discovered that > unmodifiable lists are not serializable: I think it's worth a JIRA for a > 4.0.x / 4.1, doesn't it? > > > > I was not able to make the JSTL stuffs completely work. The solution is > partly written in scriptlet in the JSP page. Here is the JIRA: > https://issues.jasig.org/browse/CAS-1448 and the pull: > https://github.com/Jasig/cas/pull/430. > > > > Feedbacks are welcome. > > Thanks. > > Best regards, > > Jérôme > > > > > > 2014-05-05 11:29 GMT+02:00 Jérôme LELEU <lel...@gmail.com>: > > Hi, > > > > OK. Noticed. > > Though, another test leads me to find a strange behaviour. If you have a > user attribute with commas (like "Jérôme, LELEU"), two attributes will be > returned instead of one. > > It comes from the fact that the success validation JSP page uses the > forEach (of the JSTL) where Strings delimited by commas are considered as > multiple elements. > > > > I will provide a fix before doing the release. > > Thanks. > > Best regards, > > Jérôme > > > > > > > > 2014-05-01 20:28 GMT+02:00 Robert Oschwald <robertoschw...@googlemail.com > >: > > ok with me. > > Whoever creates the release, please merge my PL in, first. > > > > Thanks, > > Robert > > Sent while mobile. > > > Am 01.05.2014 um 17:24 schrieb Misagh Moayyed <mmoay...@unicon.net>: > > Sounds good to me. Shall we put down Monday May 5th then? > > > > I’ll take care of javadocs, documentation, and stake a stab at updating > the protocol doc over at http://www.jasig.org/cas/protocol once v3 is > released. > > > > *From:* Robert Oschwald > [mailto:robertoschw...@googlemail.com<robertoschw...@googlemail.com>] > > *Sent:* Thursday, May 01, 2014 1:01 AM > *To:* cas-dev@lists.jasig.org > *Subject:* Re: [cas-dev] [cas-user] Schedule for CAS 4.0 > > > > on monday, I will commit the spec as 3.0 release as well. > > Sent while mobile. > > > Am 01.05.2014 um 09:54 schrieb Jérôme LELEU <lel...@gmail.com>: > > Hi, > > > > Misagh has just merged the last fix for 4.0 ( > https://github.com/Jasig/cas/pull/427). > > I will cut the release next week: on Monday (4/5/14) or Wednesday (4/7/14) > if everyone is ok. > > Thanks. > > Best regards, > > Jérôme > > > > > > 2014-04-17 18:26 GMT+02:00 Misagh Moayyed <mmoay...@unicon.net>: > > Yes that’s the thought. 28th would also be fine. There has been some > discussion on #246, and so as soon as we are able to resolve that, we > should be ok to proceed with GA, if the timing is acceptable. > > > > *From:* Jérôme LELEU [mailto:lel...@gmail.com] > *Sent:* Thursday, April 17, 2014 1:17 AM > *To:* cas-dev@lists.jasig.org > *Subject:* Re: [cas-dev] [cas-user] Schedule for CAS 4.0 > > > > Hi, > > > > Are you proposing to cut the final release (GA) on April, the 25th? I > agree, it's time to release the 4.0, even if it could be done one or two > weeks later... > > > > BTW, I'm willing to do the release, but as I'm in holidays, I can only > handle that from April, the 28th. > > > > Thanks. > > Best regards, > > Jérôme > > > > > > 2014-04-16 19:22 GMT+02:00 Misagh Moayyed <mmoay...@unicon.net>: > > Team, > I suppose the last change that we need to review and take action on is the > following pull: > https://github.com/Jasig/cas/pull/426 > > May I suggest that once the fate of this pull is decided, we'd take action > to proceed with the GA? And with that, could we perhaps agree on a > timeline, or say, Friday the 25th? This would give us 3 weeks before the > last RC which should be enough time to weed out issues. > > Misagh > > > -----Original Message----- > > From: Misagh Moayyed [mailto:mmoay...@unicon.net] > > Sent: Wednesday, April 02, 2014 12:06 PM > > To: 'cas-dev@lists.jasig.org' > > Subject: RE: [cas-dev] [cas-user] Schedule for CAS 4.0 > > > > Also, I realize now it makes better sense for the build to check for > commit > > messages and adherence to other conventions *after* it's been able to > > successfully build and test the pull. We would have been able to capture > the > > failure in advance. > > > > > -----Original Message----- > > > From: Misagh Moayyed [mailto:mmoay...@unicon.net] > > > Sent: Wednesday, April 02, 2014 12:02 PM > > > To: cas-dev@lists.jasig.org > > > Subject: RE: [cas-dev] [cas-user] Schedule for CAS 4.0 > > > > > > Another issue; pull #415 [1] broke the following test in > cas-server-core: > > > MultifactorAuthenticationTests#testAllowsAccessToHighSecurityServiceWi > > > thPa > > > sswordAndOTPViaRenew() > > > > > > This is where the test failure comes from: > > > > > > if (!(current.getPrincipal().equals(original.getPrincipal()) > > > && current.getAttributes().equals(original.getAttributes()))) { > > > throw new MixedPrincipalException(current, > > > current.getPrincipal(), original.getPrincipal()); } > > > > > > The comparison on authentication attribute fails. What is the > intention > > here? > > > Should the principal attributes be compared if we are checking for > > > mixed principal conditions? If so, should that just be captured inside > > > the > > > equals() of SimplePrincipal? > > > > > > [1] https://github.com/Jasig/cas/pull/415 > > > > > > > -----Original Message----- > > > > From: Misagh Moayyed [mailto:mmoay...@unicon.net] > > > > Sent: Wednesday, April 02, 2014 10:10 AM > > > > To: 'cas-dev@lists.jasig.org' > > > > Subject: RE: [cas-dev] [cas-user] Schedule for CAS 4.0 > > > > > > > > Excellent. I'll get going. > > > > > > > > > -----Original Message----- > > > > > From: Marvin Addison [mailto:marvin.addi...@gmail.com] > > > > > Sent: Wednesday, April 02, 2014 10:04 AM > > > > > To: cas-dev@lists.jasig.org > > > > > Subject: Re: [cas-dev] [cas-user] Schedule for CAS 4.0 > > > > > > > > > > > Thanks. Keep us posted on the progress please. > > > > > > > > > > Ldaptive 1.0.3 has been released and is available in Maven Central > > > > > [1], so we should be good to bump the version and move forward. > > > > > > > > > > M > > > > > > > > > > http://search.maven.org/#artifactdetails%7Corg.ldaptive%7Cldaptive > > > > > %7 > > > > > C1 > > > > > .0.3%7C > > > > > jar > > > > > > > > > > -- > > > > > You are currently subscribed to cas-dev@lists.jasig.org as: > > > > > mmoay...@unicon.net To unsubscribe, change settings or access > > > > > archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev > > > > > > -- > > > You are currently subscribed to cas-dev@lists.jasig.org as: > > > mmoay...@unicon.net To unsubscribe, change settings or access > > > archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev > > -- > You are currently subscribed to cas-dev@lists.jasig.org as: > lel...@gmail.com > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > > > > > > -- > > You are currently subscribed to cas-dev@lists.jasig.org as: > mmoay...@unicon.net > > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > > -- > > You are currently subscribed to cas-dev@lists.jasig.org as: lel...@gmail.com > > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > > > > -- > > You are currently subscribed to cas-dev@lists.jasig.org as: > robertoschw...@googlemail.com > > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > > > > -- > > You are currently subscribed to cas-dev@lists.jasig.org as: > mmoay...@unicon.net > > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > > > > > > -- > > You are currently subscribed to cas-dev@lists.jasig.org as: > robertoschw...@googlemail.com > > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > > -- > > You are currently subscribed to cas-dev@lists.jasig.org as: lel...@gmail.com > > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > > > > > > > > -- > > You are currently subscribed to cas-dev@lists.jasig.org as: > mmoay...@unicon.net > > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > > -- > > You are currently subscribed to cas-dev@lists.jasig.org as: lel...@gmail.com > > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > > > > > > > > -- > > You are currently subscribed to cas-dev@lists.jasig.org as: > mmoay...@unicon.net > > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > > -- > > You are currently subscribed to cas-dev@lists.jasig.org as: lel...@gmail.com > > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > > > > > > > > -- > > You are currently subscribed to cas-dev@lists.jasig.org as: > mmoay...@unicon.net > > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > > -- > You are currently subscribed to cas-dev@lists.jasig.org as: lel...@gmail.com > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > > -- You are currently subscribed to cas-dev@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-dev
