Error SAML implementation

[Christian]

Good morning, could someone help me with the migration of CAS in gradle 6.4.x to 6.5.x,
I am trying to update it and I get an error with the implementation of SAML and it is that when I execute this action
./gradlew --refresh-dependencies
it works fine but when I run the build I get a giant error saying that it does not find some classes example:
error: package org.apereo.cas.support.saml does not exist
import org.apereo.cas.support.saml.OpenSamlConfigBean;
This also happens to me in other imports. I don't know what could be happening and I can't find any documentation for this error.

[Mohamed Amdouni]

Hello,

I think that you should go for a more recent version and use Cas initializer to generate you overlay 

https://getcas.apereo.org/ui

If you want to keep this version try to generate from cas initializer then check for missing dependencies by comparing the gradle files… 

Best regards. 

--
- Website: https://apereo.github.io/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
---
You received this message because you are subscribed to the Google Groups "CAS Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cas-user+u...@apereo.org.
To view this discussion visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/918fc43e-a941-4658-9acc-a14b48364a81n%40apereo.org.

[Christian]

Hello
Mohamed Amdouni, thanks for answering, even so I don't know if it would be a good idea at all. I have a question here.
Could I make this version change without any problem? The fact is that this project has many changes and I don't know if it would give me more problems. As a professional, what do you think I should do?

Thank you very much, best regards

[Mohamed Amdouni]

Hello,

I recommend you to migrate to the newer version for many reasons;

- 6.x versions use spring boot 2.x and spring boot 2 is no longer supported, so if there is a security issue it would be hard to fix it alone…

- same thing for tomcat or jetty versions.

- problems encountered with recent versions are very likely solved by the community, but for old versions no one will investigate it …

You will have something to fix after any migration, for example I spent a couple of months to migrate from 5.x to 6.6.x … what I did is 

- read all release notes, and note the breaking changes … in my case the most relevant ones are :

* change  about saml configurations tables : should export and reimport the existing services 

* change in the timeout : spring clients that uses a default timeout of 2 hours should update their bean configuration or update the cas hard timeout to less than 2 hours  

* changes in the packages : the new version uses gradle instead of maven and should declare additional firewall rules to download gradle dependencies 

* some regressions in cas management GUI but you have always the rest endpoints for workarounds …

So migration without problems does not exist 😢

Good luck 🤞 

Best regards.