+1 for granting CAS server committership to Jérôme, with my congratulations and
gratitude for this OAuth module contribution.
+1 for including OAuth module in the 3.5 release.
Andrew
On Feb 22, 2012, at 9:45 AM, Marvin S. Addison wrote:
>
>> Given Jérôme's excellent contribution, his collabo
Ah yes i should have read better, i just asked the question too fast. In
fact you said, remove service= and pass extra parameters.
That's great. Still didn't have time to test, but be sure i will.
And thanks again !
Frederic
On Wed, Feb 22, 2012 at 9:22 PM, jleleu wrote:
> Even when the OpenId
Wow thanks a lot! I wouln't expect you would remember this. :D
I will have a look at your approach. Do you know if,configured this way,
cas can also continue to serve as a regular cas server ?
Thx again !
Frédéric
Le 22 févr. 2012 11:35, "jleleu" a écrit :
> Thanks for your trust
>
> --
Given Jérôme's excellent contribution, his collaboration on the
mailing list, jira, and github, his willingness to maintain the OAuth
module and help people use it, and his compliance with the Jasig
licensing policy, I move to provide him with committer access to the
Jasig CAS repo and include O
Items currently listed for 3.5 for which no work has
been done or is planned have been moved to the wish list. (Marvin,
this ended up being two items you had committed to, if I moved these
in error please let me know.)
I moved the issue regarding monitoring and management back onto the
roadma
Thanks for your trust
-
Frédéric,
I remember you get some trouble with CAS OpenId module.
I make it work and understand how it works globally.
First, I create a web app demo inspired from :
http://www.ibm.com/developerworks/java/library/j-openid/.
You have to fil
Congrats, Jerome !
And nice to see OAuth coming to cas :)
Fred
On Tue, Feb 21, 2012 at 11:05 PM, William G. Thompson, Jr. wrote:
> Given Jérôme's excellent contribution, his collaboration on the
> mailing list, jira, and github, his willingness to maintain the OAuth
> module and help people use
Given Jérôme's excellent contribution, his collaboration on the
mailing list, jira, and github, his willingness to maintain the OAuth
module and help people use it, and his compliance with the Jasig
licensing policy, I move to provide him with committer access to the
Jasig CAS repo and include OAut
On Tue, Feb 21, 2012 at 8:44 AM, William G. Thompson, Jr.
wrote:
> Jérôme,
>
> I'm excited about the prospects of OAuth support shipping with 3.5.
> Couple of questions:
>
> a) Can you commit to supporting the module (fix bugs, answer
> questions, evaluate patches, etc) going forward?
>
> b) Does
Jérôme,
I'm excited about the prospects of OAuth support shipping with 3.5.
Couple of questions:
a) Can you commit to supporting the module (fix bugs, answer
questions, evaluate patches, etc) going forward?
b) Does the module fit into 3.5 based on the release strategy?
https://wiki.jasig.org/dis
Folks,
This is a 3.5 release planning update.
This afternoon I executed the steps previously agreed upon in this thread:
* trimmed the 3.5 roadmap to reflect only work that is in progress
or completed. Items currently listed for 3.5 for which no work has
been done or is planned have been moved
Merge my work into master immediately following 3.5 release so it goes into
the next release, whatever its name and timeline, and refactor the LPPE work
to accommodate the API changes.
The above compromise respects my desire to move forward with API changes
that support present (password expirati
On Wed, Feb 15, 2012 at 9:38 AM, Marvin S. Addison
wrote:
>> What do you suggest?
>
>
> The following compromise:
>
> Merge my work into master immediately following 3.5 release so it goes into
> the next release, whatever its name and timeline, and refactor the LPPE work
> to accommodate the API
What do you suggest?
The following compromise:
Merge my work into master immediately following 3.5 release so it goes
into the next release, whatever its name and timeline, and refactor the
LPPE work to accommodate the API changes.
The above compromise respects my desire to move forward wit
On Tue, Feb 14, 2012 at 1:24 PM, Marvin S. Addison
wrote:
>
>> Regarding the LPPE feature thread, can you be more precise about what
>> needs to be tied up?
>
>
> Scott spoke up on
> https://groups.google.com/forum/#!topic/jasig-cas-dev/E9c68eIKK7Q and voiced
> support for my approach to password
Regarding the LPPE feature thread, can you be more precise about what
needs to be tied up?
Scott spoke up on
https://groups.google.com/forum/#!topic/jasig-cas-dev/E9c68eIKK7Q and
voiced support for my approach to password expiration. We need to hash
out a compromise.
M
--
You are curren
On Mon, Feb 13, 2012 at 4:02 PM, Marvin Addison
wrote:
>> Unless, there are objections I plan to execute the following early next week:
>
> Objection. There's open discussion on the thread "LPPE feature" that
> needs to be tied up before we proceed. I'm hopeful we can resolve the
> matter in a t
> Unless, there are objections I plan to execute the following early next week:
Objection. There's open discussion on the thread "LPPE feature" that
needs to be tied up before we proceed. I'm hopeful we can resolve the
matter in a timely fashion with some focused discussion, but it's a
blocker a
I'm keen on helping us move towards the 3.5 release for this Spring
(RC1 3/20/12?).
Unless, there are objections I plan to execute the following early next week:
* trim up the roadmap for 3.5 to reflect only work that is in progress
or completed. Items currently listed for 3.5 for which no work
On Wed, Jan 11, 2012 at 5:27 PM, Andrew Petro wrote:
> Hi,
>
>> Would be great to also hear from Scott and Andrew.
Scott? Your the only one left who hasn't weighed in.
Bill
>
>
> I agree that I think the current state is master branch is marching towards
> 3.5, and 3.4. x branch is maintena
FWIW, here's a great read about one possible Git branching model and a Git
extension to support it called git-flow:
http://nvie.com/posts/a-successful-git-branching-model/
http://jeffkreeftmeijer.com/2010/why-arent-you-using-git-flow/
Food for thought.
Cheers,
Dmitriy.
On Wed, Jan 11, 2012 at
Hi,
> Would be great to also hear from Scott and Andrew.
I agree that I think the current state is master branch is marching towards
3.5, and 3.4.x branch is maintenance for 3.4.x marching towards 3.4.12, and
3.3.x branch stands ready as the place to work on, say, a critical fix for
3.3.x.
On Wed, Jan 11, 2012 at 12:53 PM, Marvin Addison
wrote:
>> * master - dev branch of the next release (currently marching towards 3.5)
>> * 3.4.x - dev branch for a point or security release of the 3.4.x line
>> once a new minor version is cut (e.g. 3.5)
>> * 3.3.x - dev branch for a point or secur
> * master - dev branch of the next release (currently marching towards 3.5)
> * 3.4.x - dev branch for a point or security release of the 3.4.x line
> once a new minor version is cut (e.g. 3.5)
> * 3.3.x - dev branch for a point or security release of the 3.3.x line
That's where we landed with ve
On Wed, Jan 11, 2012 at 10:38 AM, Marvin Addison
wrote:
>> I see that CAS 3.4.11 [1] includes fixes not present in the 3.4.x
>> maintenance branch [2].
>
> I don't think we have become used to the process needed to merge
> commits to master into maintenance branches. I've done a few in the
> pa
On Mon, Jan 9, 2012 at 1:05 PM, Andrew Petro wrote:
> Howdy,
>
> I see that CAS 3.4.11 [1] includes fixes not present in the 3.4.x
> maintenance branch [2].
>
> E.g., per CAS-1055 [3] LdapUtils was moved from cas-server-core to
> cas-server-support-ldap and improved as regards its encoding of L
> I see that CAS 3.4.11 [1] includes fixes not present in the 3.4.x
> maintenance branch [2].
I don't think we have become used to the process needed to merge
commits to master into maintenance branches. I've done a few in the
past, but I haven't done any recently and I can imagine it's quite
s
27 matches
Mail list logo
