Re: [cas-user] Re: Submit a CAS evolution for 6.6.12

2023-10-12 Thread Jérémie
Hi, We received this email by contacting it : -- Hi, We're writing to let you know that the group you tried to contact (cas-dev) may not exist, or you may not have permission to post messages to the group. A few more details on why you weren't able to post: * You might have spelled or

Re: [cas-user] Re: Submit a CAS evolution for 6.6.12

2023-09-25 Thread Ray Bon
Jérémie, There is a cas developer list https://apereo.github.io/cas/Mailing-Lists.html#cas-developer-list-cas-devapereoorg Ray On Mon, 2023-09-25 at 00:48 -0700, Jérémie wrote: Notice: This message was sent from outside the University of Victoria email system. Please be cautious with links

[cas-user] Re: Submit a CAS evolution for 6.6.12

2023-09-25 Thread Jérémie
Yeah I see but I don't know how to split this much more. I've contacted a few person also that tells me that this won't pass in 6.x but more in 7.x. How can I be sure that this feature will be (when fixed) validated for Cas, or how will I know in which release (and when). We're working on

[cas-user] Re: Submit a CAS evolution for 6.6.12

2023-09-08 Thread John
You have basically one large commit for all changes, its much easier for apereo to see what and where is being changed if you make a commit for each section of changes. Also, why is there authy stuff in the mfa module, should probably be renamed, the classes, etc.. to okta, for example,