Hi Baron,
We are running CAS version 6.5.9 and I was able to set a skew allowance
value per service as follows:
{
"@class" : "org.apereo.cas.services.RegexRegisteredService",
"serviceId" : "^https://.*";,
"name" : "Sample",
"id" : 10,
"skewAllowance": 40
}
Note: Setting a negative
Hi Robert,
There used to be a bug in CAS where a wildcard SAML service would catch
undefined CAS services.
That issue should have been fixed in releases 6.4.0 and up.
What version of CAS are you using?
Thanks
Olivier B.
ITS Middleware
Florida State University
On Friday, June 24, 2022 at 12:51
Hi Pranee,
The error you have is seems to be that the CAS Management cannot connect to
mdq.incommon.org:443. Have you checked if you have access to that address
from your local machine running CAS Mgmt? Can you telnet/ping that site?
If you are not able to open access, you can try to add the fol
Purush,
Have you tried with 6.4.0-RC6 ?
Thanks.
Olivier
On Monday, August 16, 2021 at 10:03:35 AM UTC-4 Purush wrote:
> Was anyone able to get CAS 6.4.0 to work with SAML2 and CAS as the idP? We
> are still unable to get this to work and are not sure where to look?
>
> Our setup:
> Service A
Hi Stephane,
I have experienced the same behavior with the 6.4.0-SNAPSHOT (CAS Commit
Id: 10186408101c29180fa4818b788f47ecbaa86101) version. A fix has been
released and should be available today for the 6.4.0-SNAPSHOT, I hope for
you that ig the fix is working, it will also be applied to the 6.
Hi,
I noticed a change in your release calendar for 6.4.
If I'm not mistake 6.4.0 was supposed to be released after 6.4-RC5
somewhere early July and now when checking the release calendar again, I
noticed that a 6.4-RC6 had been introduced and that the 6.4.0 release date
was pushed to August
