Just an FYI, in case someone else run's into this.
The solutions was simply to remove the management. prefix from the
server.ssl directives ala.
server.ssl.key-store: file:
server.ssl.key-store-password:
server.ssl.key-password:
I'm certain management.server was what I used for 6.0.2 and
I give up.
I've tried everything. I have no clue. Even again did fresh git clone
and immediate build.sh run with the following world readable
management.properties
cas.server.name=https://xx.xxx.xxx
cas.server.prefix=${cas.server.name}/cas
Colin,
I run it in a separate tomcat on my local (that is where I am in the upgrade
process). Our sysadmins have switched to multiple applications managed, not run
by, a single tomcat. I have not set up my local for that yet. It involves the
difference between CATALINA_BASE and CATALINA_HOME.
Colin,
Have you tried running in a standalone tomcat?
I have never used the embedded one. We front our tomcat with apache and connect
with ajp.
Ray
On Wed, 2020-09-02 at 12:33 -0400, Colin Ryan wrote:
So as a follow-on Phase 3. I moved this whole thing to a Linux environment in
the off
So as a follow-on Phase 3. I moved this whole thing to a Linux
environment in the off chance that macOS's 10.15 funky overlay
filesystems were causing me grief.
No joy.
Can someone do me a favour and just confirm that the
cas-management-overlay out of the box build will work with a self
Ray,
I'll try it but the public key for it already is as it's the same cert.
I was using for the /cas deployment itself in an external tomcat
deployment. It was complaining about un-trusted certs until I did that.
Coln
On 8/24/20 3:47 PM, Ray Bon wrote:
Colin,
Maybe add your certificate
Colin,
Maybe add your certificate to the java ketstore.
https://docs.oracle.com/cd/E54932_01/doc.705/e54936/cssg_create_ssl_cert.htm#CSVSG180
Ray
On Mon, 2020-08-24 at 15:25 -0400, Colin Ryan wrote:
Notice: This message was sent from outside the University of Victoria email
system. Please be
Folks,
So I've still not managed to move past this. Even even started from scratch.
git clone https://github.com/apereo/cas-management-overlay.git
git checkout 6.0.x
./build.sh clean
./build.sh run - breaks because it can't seem to find some of the
required components for the 6.0.x
Hi,
Yes, I use PostgreSQL to store services and tickets.
I actually try to use LDAP to auth my users in CAS Management, but actually
it doesn't work :
WARN [org.apereo.cas.mgmt.authz.CasRoleBasedAuthorizer] - Unable to
authorize access, since the authenticated profile [#CasProfile# | id:
Hi Mr Julien Sabatier,
I have read your cas-management configuration and I guessed your
cas-management authen user from LDAP and store service registry to
PostgreSQL.
Is that right?
You resolved your problem.
Can you show me your cas-managment, cas-overlay and service registry in
detail?
Thank you
I solved the problem. It was that I didn't added
"cas-server-support-discovery-profile" to my CAS dependencies at
compilation, so the discovery service wasn't available.
Thanks for your help.
Now my problem is that I want to use ldap for CAS Management auth, and for
this I need to include
You probably aren't waiting long enough?
2020-08-17 09:06:54,686 DEBUG [org.apache.http.impl.execchain.MainClientExec] -
Executing request GET /actuator/discoveryProfile HTTP/1.1
It's trying to make a connection to your CAS system. Looks like from your logs
it hasn't time out, and thus hasn't
12 matches
Mail list logo
