There should be output right after audit line, SERVICE_TICKET_VALIDATED.
You could also set cas.log.level to debug or trace.
Ray
On Fri, 2020-01-24 at 12:55 -0800, crdaudt wrote:
Hmmm, no debug lines are being added to the log. Either I do not have the
debug line entered correctly in
Thanks Andy for the information. We spent some more time this morning
troubleshooting the behavior and have discovered the reason for this
behavior. It seems that the ticket granting cookie is encoded and is not
just the TGT, it is TGT+Client IP+Browser Agent. When a call comes into
we are using a system-wide OpenSSL
and only one is installed
apt-cache policy openssl
returns:
Installed: 1.0.2g-1ubuntu4.15
On Fri, Jan 24, 2020 at 3:05 PM Colin Ryan wrote:
> This reeks of some mismatch with your OpenSSL libraries.
>
> Are you using the system wide OpenSSL and associated SSL
Hmmm, no debug lines are being added to the log. Either I do not have the
debug line entered correctly in log4j2.xml, or none of these attributes are
being released.
Here is a portion of my log4j2.xml:
---BEGIN PORTION OF log4j2.xml---
...
This reeks of some mismatch with your OpenSSL libraries.
Are you using the system wide OpenSSL and associated SSL lib's or are
you rolling your own OpenSSL as well.
If the latter be sure that pkg-config and other ./configure directives
are actually using your own libraries versus the system
I am adding the error log:
Jan 24 18:08:51 ip-172-31-0-113 systemd[1]: Starting LSB: Apache2 web
server...
-- Subject: Unit apache2.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Hello,
We are trying to set up a CAS Client on an ec2, running ubuntu 16LTS, using
the mod_auth_cas project. we have gotten everything downloaded, complied,
built and installed as per the README but when we try to start with:
sudo systemctl enable apache2
we get:
undefined symbol:
Hello everyone,
We are trying to set up a CAS Client on an ec2, running ubuntu 16LTS, using
the mod_auth_cas project. we have gotten everything downloaded, complied,
built and installed as per the README but when we try to start with:
sudo systemctl enable apache2
we get:
undefined
Carl,
This debug line will let you know what is being returned:
Ray
On Fri, 2020-01-24 at 06:42 -0800, crdaudt wrote:
Adding org.apereo.cas:cas-server-support-saml to the build certainly made a
difference: CAS now recognizes the JSON entry for our Ellucian Banner related
I found a reason of this exception.
My 6.0.3 version of CAS uses application.properties from
*src\main\resources*. This exception disappears if I copy-paste content of
this file to *etc\cas\config\cas.properties* and delete
*application.properties* file.
--
- Website:
Thanks Mike. Unfortunately, using the attributeReleasePolicy you stated in
my JSON file and the ticketidSaml2=false setting in my cas.properties made
no difference.
I am grasping for any ideas, and appreciate your jumping in with them.
Carl
On Friday, January 24, 2020 at 10:01:28 AM UTC-5,
Carl,
I have this working with 6.0.x But I'm limiting the release to just
UDC_IDENTIFIER like this:
"attributeReleasePolicy" : {
"@class" :
"org.apereo.cas.services.ReturnAllowedAttributeReleasePolicy",
authorizedToReleaseCredentialPassword: false
Adding org.apereo.cas:cas-server-support-saml to the build certainly made a
difference: CAS now recognizes the JSON entry for our Ellucian Banner
related service.
Unfortunately, I am still not out of the woods. The Banner service is now
reporting "HTTP Status 500 -
Oh, no -- What I have is the following. I have:
compile "org.apereo.cas:cas-server-support-saml-idp:${casServerVersion}"
...but I do not have:
compile "org.apereo.cas:cas-server-support-saml:${casServerVersion}"
I will let you know what I find after adding, re-building, and testing.
Carl
On
Yes, that line is included in my build.gradle file.
On Thursday, January 23, 2020 at 7:10:16 PM UTC-5, rbon wrote:
>
> Carl,
>
> Do you have saml support enabled:
> compile "org.apereo.cas:cas-server-support-saml:${casServerVersion}"
>
> Ray
>
>
> On Thu, 2020-01-23 at 15:32 -0800, crdaudt wrote:
Good morning!
When requesting a password reset from the main CAS login page (not via
service) you receive a link like the following:
https://casdev.hvcc.edu/cas/login?pswdrst=TST-1-ATe9S6Bym5Vq8Prk6lMa9Pr86war7Ijf
However, if selected from a service's login page, you get the following
16 matches
Mail list logo