Re: [cas-user] CAS, 4.1.7, JoseException: A JWS Compact Serialization must have exactly 3 parts separated by period ('.') characters

Can you point me to the right direction as to where this problem can be fixed? Is this some configuration issue I missed? Or, it this outside of CAS, such as a browser issue? Yan On Fri, Apr 22, 2016 at 9:23 PM, Misagh Moayyed wrote: > It refers to the ticket-granting

RE: [cas-user] CAS, 4.1.7, JoseException: A JWS Compact Serialization must have exactly 3 parts separated by period ('.') characters

It refers to the ticket-granting cookie. Its value cannot be parsed. From: cas-user@apereo.org [mailto:cas-user@apereo.org] On Behalf Of Yan Zhou Sent: Friday, April 22, 2016 2:11 PM To: CAS Community Subject: [cas-user] CAS, 4.1.7, JoseException: A JWS Compact

[cas-user] CAS, 4.1.7, JoseException: A JWS Compact Serialization must have exactly 3 parts separated by period ('.') characters

Hi there, With my CAS 4.1.7 overlay, getting this exception intermittently. I do not know which value this exception is referring to. The host.name entry in cas.properties is correctly specified. Any suggestions? Yan My cas.properties look like this, host.name does have the FQDN.

RE: [cas-user] odd error setting up database auth handler cas 4.2.0

https://github.com/Jasig/cas/issues/1691 From: cas-user@apereo.org [mailto:cas-user@apereo.org] On Behalf Of Nancy Snoke Sent: Friday, April 22, 2016 11:39 AM To: cas-user@apereo.org Subject: [cas-user] odd error setting up database auth handler cas 4.2.0 I am having an odd error when

[cas-user] odd error setting up database auth handler cas 4.2.0

I am having an odd error when trying to add a queryDatabaseAuthenticationHandler to a CAS 4.2.0 server. The error seems to indicate it is trying to set up queryAndEncodeDatabaseAuthenticationHandler as opposed to a queryDatabaseAuthenticationHandler. I already have ldap set up, and am adding

RE: [cas-user] Re: 4.x SAML documentation

Great. Look forward to it. Speaking for myself, my only semi-obvious requirements for considering this sort of change are that the dependencies/libraries your extension depends on must be available in some sort of central repository, preferably maven central, and that we should have access

[cas-user] more attributes returned than allowed

While we have all of our services set for ReturnAllowedAttributeReleasePolicy, The CAS response received by the app includes all attributes that were resolved. We logged this: 2016-04-22 10:31:10,065 DEBUG [http-bio-8080-exec-29] [org.jasig.cas.CentralAuth enticationServiceImpl] - Attribute

Re: [cas-user] Re: 4.x SAML documentation

> > I've been holding off on trying the snapshots so far, due mostly to other > things on my plate, but also because I'm waiting for 4.3.x and MFA to get a > little closer, as we want that, too. I sorta kinda get the overlays and > stuff, and even some coding, in that I managed to figure out

[cas-user] CAS migrating to new version

Hello everyone I am using Jasig-CAS to achieve Single Sign In and Single Sign Out for multiple applications I was using cas-server as parent(version 4.0.0) and I have updated it to 4.1.7 as* release build for cas-server is upto 4.1.7 at http://oss.sonatype.org/content/repositories/releases/

Re: [cas-user] Releasing credential

It is working now! Thank you guys for the fast response! Here is a PR to update the doc of 4.2.x: https://github.com/Jasig/cas/pull/1707 Cheers! -- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop