CAS 4.2.3 Release Announcement

[Misagh Moayyed]

CAS Community,

 

CAS version 4.2.3 [1] has been released and should shortly find its way into central repositories, if not already. We encourage you to deploy this release into your own CAS maven overlay environment and provide feedback. Upgrading from a 4.2.x deployment should be painless.

 

Misagh

 

[1] https://github.com/Jasig/cas/releases/tag/v4.2.3

 

[wil.i.am]

Is anyone else running into the issue where org.apache.shiro:shiro-core:1.2.5 has an invalid encoding of UTF8 (which should be UTF-8)?

[wil.i.am]

CAS 4.2.3 uses Apache Shiro 1.2.5.

Is anyone else running into the issue where org.apache.shiro:shiro-core:1.2.5 has an invalid encoding of UTF8 (which should be UTF-8)?

On Monday, June 27, 2016 at 1:04:49 AM UTC-4, Misagh Moayyed wrote:

[William]

Has anyone tried CAS 4.2.3 and ran into the invalid UTF8 encoding for Apache Shiro 1.2.5?  Am I the only person that has ran into this?

Referece: https://issues.apache.org/jira/browse/SHIRO-567

[siim.r...@gmail.com]

Hmm... after upgrading to 4.2.3 authentication process succeeds, but no tickets (TGT or ST) aren't created. I don't get any error messages also... I'am using JPA registries.


Siim

--
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 post to this group, send email to cas-...@apereo.org.
Visit this group at https://groups.google.com/a/apereo.org/group/cas-user/.
To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/003201d1d031%246c319a20%244494ce60%24%40unicon.net.
For more options, visit https://groups.google.com/a/apereo.org/d/optout.

[William]

That's strange because I can see the cas-server-core is pointing to org.apache.shiro:shiro-core:1.2.5 which has an invalid encoding:

http://central.maven.org/maven2/org/jasig/cas/cas-server-core/4.2.3/cas-server-core-4.2.3.pom

[siim.r...@gmail.com]

It's a bug. If using jpaServiceRegistryDao then whole ticket generation process fails. I upgraded my previous issue, by adding jpaServiceRegistryDao. (https://github.com/siim-romanov/cas-issues/commit/704618c188b1e9319d63b67bfc3bec0286ff72df )

If using it with 4.2.2 loggin succeeds and tickets will be created, but not with version 4.2.3. It works with jsonServiceRegistry.

esmaspäev, 27. juuni 2016 8:04.48 UTC+3 kirjutas Misagh Moayyed:

--

[siim.r...@gmail.com]

It's seems to be a bug. If using jpaServiceRegistryDao then whole ticket generation process fails. I upgraded my previous issue, by adding jpaServiceRegistryDao. (https://github.com/siim-romanov/cas-issues/commit/704618c188b1e9319d63b67bfc3bec0286ff72df )

If using it with 4.2.2 loggin succeeds and tickets will be created, but not with version 4.2.3. It works with jsonServiceRegistry.

[siim.r...@gmail.com]

So I turned DEBUG on found that the problem is transaction manager. If user uses both cas-server-support-jpa-ticket-registry and cas-server-support-jpa-service-registry then there will be created two transaction managers.
Because of that spring throws org.springframework.beans.factory.NoUniqueBeanDefinitionException: No qualifying bean of type [org.springframework.transaction.PlatformTransactionManager] is defined: expected single matching bean but found 2:

Should I open new issue on github?

[Dmitriy Kopylenko]

It’s been fixed in the master and should be available in 4.2.4: https://github.com/apereo/cas/issues/1866

Cheers,

D.

To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/187252bf-52bd-4809-8ed7-0277637ccc56%40googlegroups.com.