Hi Luis,
This is a known behavior, it seems CAS management is also using the
scheduled reloading of all service definitions just like CAS server itself.
The effect at CAS management is, that changes are not immediately reflected
in the GUI. You may try the reload button to see the changes.
I checkout to version 6.4 and run it successfully with same
management.properties and same dependencies.
But version 6.5 and 6.6 have return same error on tasks run:
2023-12-23 16:22:14,742 WARN
[org.springframework.boot.web.servlet.context.AnnotationConfigServletWebServerApplicationContext]
I'am facing the same error. Did you fix it ?
On Wednesday, August 18, 2021 at 1:15:17 AM UTC soli...@gmail.com wrote:
> I was trying to setup cas-management with
> https://github.com/apereo/cas-management-gradle-overlay at branch 6.3.x,
> ./gradlew run give me following warnning:
>
>
Hi same thing here.
I've successfuly installed and run cas 6.6.7 on the same machine
Did you copy the management configuration in the /etc/cas/config folder ?
Le mercredi 18 août 2021 à 03:15:17 UTC+2, soli...@gmail.com a écrit :
> I was trying to setup cas-management with
>
Same here with CAS-MGMT 6.6.1 and CAS 6.6.6.
Switched back to RegexRegisteredService for now.
On Tuesday, 6 December 2022 at 10:15:31 UTC+1 BenDDD wrote:
> Hello,
>
> Thank you Fabio for your feedback.
>
> Does anyone have a solution to this problem or do I have to open an issue?
>
> Le lundi 5
Same here.
The effect here is, that in ngOnInit() line 84 it is asynchronously
performing this.loadService(data.resp), but in line 89
of form.component.ts, the form is used synchronously.
Just an update on this issue. The previous issue was reported in my Test
Environment. I upgraded my Production Environment today, minus the
OIDC/Oauth2 modules, and the issue is now happening there. This seems to be
an issue with CAS-Management and not related to deploying OIDC/Oauth 2.
Ray,
That did it, thank you !!
Now I can see the main page (cas-management/management/registry) with a
menu bar on the left (CAS Services, OAuth Services ...).
But I can't do anything, and I have a new error in the log :
[org.springframework.web.util.NestedServletException: Request processing
I made a typo, it is a cas server 6.6.4
Le jeudi 9 février 2023 à 06:54:01 UTC+1, Vincent Delhommmeau a écrit :
> Hello,
>
> I am trying to set up a cas-management web application 6.6.0 on a cas
> server 6.4.0.
> After a successful cas login, this message is displayed by the
> cas-management
hi
same here, except that the CAS server does not work anymore with
"*RegexRegisteredService",
*i'm obliged to replace all my services with Cas*RegisteredService that i
can't manage with casmanagement :(*
*i test with all the last version (6.6.x)*
Le mardi 6 décembre 2022 à 10:15:31 UTC+1,
Hello,
Thank you Fabio for your feedback.
Does anyone have a solution to this problem or do I have to open an issue?
Le lundi 5 décembre 2022 à 11:56:07 UTC+1, fabiob...@gmail.com a écrit :
> Same configuration, same problem here.
> I had to switch back the service definitions to
Same configuration, same problem here.
I had to switch back the service definitions to RegexRegisteredService (and
swallow the logs warnings, for now) in order to see them in management.
Il giorno mercoledì 30 novembre 2022 alle 17:28:30 UTC+1 BenDDD ha scritto:
> Hi there,
>
> We used CAS
Hi there,
Does anyone have any idea what I might have missed that could be causing
this behavior?
Thanks in advance.
Le mercredi 30 novembre 2022 à 17:28:30 UTC+1, BenDDD a écrit :
> Hi there,
>
> We used CAS (6.6.2) and CAS-management (6.6.0).
>
> On the CAS-management web interface, if I
lanf,
Apologies, that is the the location of the local git repo; and the 6.6.x
property is:
mgmt.version-control.services-repo
If you are using json service registry:
cas.serviceRegistry.json.location=file:/etc/cas/services
Had to go through the source docs to find it.
it does not work. the application no longer launches. Here is the error:
[2022-11-10 07:55:15] [info] 2022-11-10 07:55:15,391 WARN
[org.springframework.boot.web.servlet.context.AnnotationConfigServletWebServerApplicationContext]
-
[2022-11-10 07:55:15] [info] 2022-11-10 07:55:15,456 ERROR
lanf,
This looks to be the default directory
# mgmt.services-repo=/etc/cas/services-repo
https://apereo.github.io/cas-management/6.3.x/installation/Configuration-Properties.html#properties
Have you changed it in your management.properties?
Ray
On Wed, 2022-11-09 at 02:28 -0800, lanf detroy
lanf,
You can change the group for the services directory and give it write
permissions.
sudo chgrp --recursive tomcat /etc/cas/services
sudo chmod g+w --recursive /etc/cas/services/
Ray
On Sun, 2022-11-06 at 22:46 -0800, lanf detroy wrote:
Notice: This message was sent from outside the
lanf,
If you are on linux you can use this command to see access and ownership of the
services directory (on my laptop):
ls -l /etc/cas/
total 4
drwxrwxr-x 3 rbon rbon 4096 Jun 16 18:36 services
To see the process owner for the container running cas (this is for tomcat
running, substitute your
I don't know where to look for this? What parameter to put?
Le jeudi 27 octobre 2022 à 18:37:46 UTC+2, Ray Bon a écrit :
> lanf,
>
> Check that the process that is running cas management has write access to
> the directory in the config.
>
> Ray
>
> On Thu, 2022-10-27 at 07:42 -0700, lanf
lanf,
Check that the process that is running cas management has write access to the
directory in the config.
Ray
On Thu, 2022-10-27 at 07:42 -0700, lanf detroy wrote:
Notice: This message was sent from outside the University of Victoria email
system. Please be cautious with links and
Hi Eric, would you mind posting your apache https proxy config? I may be
able to point you in the right direction to make that work.
On Tuesday, 23 August 2022 at 08:53:40 UTC-5 Mallory, Erik wrote:
> Hello,
> Is there a way to get the CAS Management Webapp to use AJP ports, I'd
> like to
Hello,
Thank you for your message, you solve my problem with the launch of
cas-management 6.3.7
Le jeudi 10 février 2022 à 17:14:21 UTC+1, petr.f...@gmail.com a écrit :
> Hello,
> Some versions of the CAS Mgmt app have an if-statement in their code that
> disables the incommon checking when
Hello,
Some versions of the CAS Mgmt app have an if-statement in their code that
disables the incommon checking when the incommon URL is empty. For example:
Thanks Olivier for your reply.
The site mdq.incommon.org:443 is blocked in my machine. I tried adding
spring.autoconfigure.exclude=org.apereo.cas.mgmt.config.CasManagementSamlConfiguration
property in cas.properties of CAS server overlay as well as
management.properties of CAS management
I was not quite done the previous email.
cas.authn.ldap[0]...
cas.authn.ldap[1]...
etc.
Ray
On Tue, 2022-02-08 at 10:13 -0800, Michael Santangelo wrote:
Notice: This message was sent from outside the University of Victoria email
system. Please be cautious with links and sensitive information.
The finalized working bit for Active Directory LDAP was:
# Working LDAP Auth
cas.authn.ldap[0].order=0
cas.authn.ldap[0].name=Active Directory
cas.authn.ldap[0].type=AD
cas.authn.ldap[0].ldapUrl=ldap://:389
cas.authn.ldap[0].validatePeriod=270
cas.authn.ldap[0].poolPassivator=NONE
Michael,
To follow up on Felix's post.
You can create multiple ldap (ldap entries, one for each ou. cas will search
them the order they are in your properties file.
Ray
On Tue, 2022-02-08 at 10:13 -0800, Michael Santangelo wrote:
Notice: This message was sent from outside the University of
I think you should use only one entry for "type". (Currently you will
probably use AUTHENTICATED)
Felix
Am 08.02.22 um 22:07 schrieb Michael Santangelo:
The finalized working bit for Active Directory LDAP was:
# Working LDAP Auth
cas.authn.ldap[0].order=0
cas.authn.ldap[0].name=Active
Are you sure, that you need to set dnFormat? If you have users in
different ou's, it will be difficult to use with a template as
cn=%s,ou=... and should not the dn be found by the searchFilter?
Felix
Am 08.02.22 um 19:13 schrieb Michael Santangelo:
I changed my config to:
Are you modifying the cas.properties created in /etc/cas or the one in your
project folder? I don't think you want to do a copyCasConfiguration on
each run as it will overwrite the cas.properies file in your /etc/cas folder
Anyhow, my config looks similar to yours. One think I did run a
I changed my config to:
cas.authn.ldap[0].order=0
cas.authn.ldap[0].name=Tech Active Directory
cas.authn.ldap[0].type=AD
cas.authn.ldap[0].ldapUrl=ldap://:389
cas.authn.ldap[0].validatePeriod=270
cas.authn.ldap[0].poolPassivator=NONE
cas.authn.ldap[0].searchFilter=sAMAccountName={user}
I am modifying the file project file not the file in the local /etc
folder. the full path is
/home//cas-management-overlay/etc/cas/config/cas.properties
On Tue, Feb 8, 2022 at 12:38 PM Pablo Vidaurri wrote:
> Are you modifying the cas.properties created in /etc/cas or the one in
> your project
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
Thanks for your intervention.
Sincerely,
Le jeudi 10 septembre 2020 à 16:38:45 UTC+2, Misagh Moayyed a écrit :
> This was an obvious mistake; sorry about that. The repo status is restored.
>
> On Thu, Sep 10, 2020 at 6:31 PM randomuser878 wrote:
> >
> > Greetings
> >
> > Can not add anything
This was an obvious mistake; sorry about that. The repo status is restored.
On Thu, Sep 10, 2020 at 6:31 PM randomuser878 wrote:
>
> Greetings
>
> Can not add anything concrete to your observation.
> This looks promising
>
Greetings
Can not add anything concrete to your observation.
This looks promising
https://apereo.github.io/cas/development/release_notes/RC2.html#dynamic-jpa-service-management
in terms of future of the component but totally unclear how does it fit
with your observation of archived
Duncan,
I know this thread is over a year old, but I have been tasked with
upgrading a (very old) CAS deployment to 5.3 and have run into the same
issue.
"Caused by: java.lang.IllegalArgumentException: More than one fragment with
the name [spring_web] was found. This is not legal with relative
Hello
Using master of cas-management release.
So far with all those changes noted by JC and parameters and permissions,
I just add this when exploding war on the webapps folder
rm -v
"SOME_PATH/cas-management/WEB-INF/lib/cas-mgmt-config-version-control-${VERSION}.jar"
rm -v
Sorry to also chime in on an old thread but I've just been trying to
upgrade to the latest cas-management overlay today and ran into similar
issues.
For the issue where *existing* services weren't showing up it might be
incorrect permissions on the git repo that is automatically generated in
The link that I provided
(https://apereo.github.io/cas/6.1.x/configuration/Configuration-Properties.html#multimapped-attribute)
shows '[type-placeholder]' in a generic definition.
# cas.authn.attributeRepository.[type-placeholder].attributes.uid=userId
The 'stub', which you referenced, and
Hello JC,
I think what you use, is not what you discribe.
cas.authn.attributeRepository.stub.attributes.udcid=UDC_IDENTIFIER
Enter code here...
This is for define a static attribute "udcid" with value "UDC_IDENTIFIER".
I think it is a bug.
I'm using 6.1.5, and after doing some investigating, I have found that when
a service name is changed the VersionControlServicesManager class calls the
checkForRename function, which builds the path and appends ".json" to the
end (with a period). This has the effect of
I know this topic is five months old, but I wanted to add what I discovered
so that it will be here if someone else finds this in a search, like I did.
I have found that the documentation that shows the two properties' syntax
referenced is wrong, unsurprisingly. The values that worked for me in
Hello,
not sure if that helps, but to disable the git tracking you'd need to set
the property
mgmt.versionControl.enabled=false
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions:
Thanh,
I ran in to the same problem and could find no way to turn off git requirement.
As such, we are still using 5.2 version.
Ray
On Mon, 2020-03-09 at 16:52 +0700, Nguyen Tran Thanh Lam wrote:
Notice: This message was sent from outside the University of Victoria email
system. Please be
Dear Mr B Ran,
I don't use git and don't enable any dependencies relevant git.
Thank you. Regards
Vào Th 2, 9 thg 3, 2020 vào lúc 16:49 B Ran đã viết:
> I remember having an issue on that one.
> Can you try this configuration ?
>
> mgmt.versionControl.servicesRepo=//etc/cas/services-repo
>
>
I remember having an issue on that one.
Can you try this configuration ?
mgmt.versionControl.servicesRepo=//etc/cas/services-repo
Make sure whatever runs cas-management has read/write access to
/etc/cas/services-repo and on the git
--
- Website: https://apereo.github.io/cas
- Gitter
I remember having an issue on that one.
Can you try this configuration ?
mgmt.versionControl.servicesRepo=//etc/cas/services-repo
Make sure whatever runs cas-management has read/write access to
/etc/cas/services-repo and on the git
Once the git repo is initialized, make sure to configure the
cas-management usually creates a git repository and then offers to push
commits made through the UI to service registries.
You can configure the location of the git repo with the property
mgmt.versionControl.servicesRepo
Assuming both CAS and cas-management are running on the same machine
I tried building from source to add more debugging, but was unable to build
without error. If I fixed one error, then another popped up. I do not have time
to chase them down.
I will come back to it, perhaps in the new year. Until then we will use an
older version.
Ray
On Fri, 2019-10-25 at
Admittedly the CAS Mgmt documentation is lagging some of the latest
refactors in the snapshots. I usually try and make an effort when GA rolls
around to try and make sure at least config properties are updated. You
can look here directly at the source of truth:
Hello
Thanks for the hint per CasManagementConfigurationProperties.java
I would like to know that too.
Thanks,
Mike
Michael Barsic
Director of Technical Architecture
Savannah College of Art and Design®
mbar...@scad.edu - www.scad.edu
On Tuesday, September 17, 2019 at 12:43:03 PM UTC-4, rbon wrote:
>
> How do I turn off version control in cas-management 6.1
Try to build cas management from
https://github.com/apereo/cas-management/releases/tag/v6.0.0-RC4 (not from
overlay)
Append dependencies to build.gradle:
compile
"org.apereo.cas:cas-server-support-jpa-service-registry:${casVersion}"
compile
Hello David
I've been going in circles for several weeks now
My case server works well it is on another vm.
Same Linux Debian operating system 10
Thank you
Best regard
Le lundi 22 juillet 2019 12:04:48 UTC+2, alain ubfc a écrit :
>
> Hello,
>
> I’ve been stuck on cas-management for several
Hello Matthew,
I just looked in /etc/cas/config ans i have the file you asked me to check.
I removed the excess line line in /etc/cas/config/management.properties
For the user casermgnt i saw that he has no right to launch tomcat when i
make the following command :
systemctl restart
Thank you for confirming that your /var mount point is rw. Also, since you
are running tomcat as root (definitely not recommended for PROD),
permissions should not be an issue. It sounds like you need to make sure
your configurations are all uniform. Specifically, that
your
Matthew,
I relanched tomcat each time as root.
So i addes the user toto in the casermgnt group.
I cheched the mounting of the partitions :
casermgnt@casermgnt:~$ cat /proc/mounts
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
udev /dev
Alain,
Your fstab file shows that /var should be mounting correctly, but a file
system can become read-only for any number of reasons. If it is in fact
read only, then any user, even root, would not be able to write to it. You
could try the following command from the directory
Check that the process is actually running as tomcat. Turn on debug logging
and see what's happening. Compare the owners and modes of the working logs
(cas) to the non-working ones (cas-management).
There's a permission that's wrong, or it's running as the wrong user, or
there's a typo in a path
Are you positive that the tomcat process is actually running as the tomcat
user?
The error message says read-only file system. Are you sure the file system
is mounted read-write? Can you create files in it?
Have you turned on debug-level logging to get a more granular idea of
what's going on?
Hello David,
Thank you for your answer.
The directory /var/log/cas-management has the following rights :
drwxr-x--- 2 tomcat adm 4096 juil. 22 09:23 cas-management
And for the filecas-management.log
-rw-r- 1 tomcat tomcat0 juil. 19 14:39 cas-management.log
That's what i did.
[2019-07-22 08:57:45] [info] 2019-07-22 08:57:45,023 main ERROR
RollingFileManager (/var/log/cas-management/cas-management.log)
java.io.FileNotFoundException:
/var/log/cas-management/cas-management.log (Read-only
file system)
Is your file system mounted read-only? Is the directory writable by the
Hello,
In fact I noticed that the/var/log/case-management file has nothing in it.
Yet I set the rights for the file cas-management.log with the chown -R
tomcat:tomcat/var/log/cas-management command.
[2019-07-22 08:57:43] [info] 2019-07-22 08:57:43,429 main ERROR Could not
create plugin of
Hello,
Sorry i had erased the message of Mailvaganam Hari by making a bad handling
:
*Is port 8443 appearing in the URL redirect? If it is – won’t match with
the ACL in the JSON file.*
Le lundi 22 juillet 2019 12:04:48 UTC+2, alain ubfc a écrit :
>
> Hello,
>
> I’ve been stuck on
Same issue here. It crashes/locks up Tomcat .
r/Chad
On Friday, May 10, 2019 at 10:15:05 AM UTC-4, Alexi Pascual wrote:
>
> hi,
>
> Has anyone managed to install without problems the ca-management- 6.0 ?. I
> have the same error, without the mongoDB configuration.
>
> Alexi.
> El 07-05-19 a
hi,
Has anyone managed to install without problems the ca-management- 6.0 ?.
I have the same error, without the mongoDB configuration.
Alexi.
El 07-05-19 a las 13:07, Mathias Rosenberg escribió:
I'm also facing the same problem, did you find some solution for it?
Mathias.
El miércoles, 27
I'm also facing the same problem, did you find some solution for it?
Mathias.
El miércoles, 27 de marzo de 2019, 6:56:34 (UTC-3), Taupasse escribió:
>
> Hello,
>
> I'm currently trying to set up the cas management webapp 6.0 against a
> working Cas 6.0 with a ticket registry in a replicated
I hope CAS Management can take attributes based on existing attributes
(*attribute
key*).
Thank David!
Pada Jumat, 05 April 2019 15.01.42 UTC+7, Fahmi L. Ramdhani menulis:
>
> Hello,
>
> How to configure the attribute list in the Attribute Release Policy
> (Return Allowed) in CAS Management?
*This problem has been Solved.*
I am forget to insert dependency to *pom.xml* in *management project*.
org.apereo.cas
cas-server-support-jdbc-drivers
${cas.version}
org.apereo.cas
cas-server-support-jpa-service-registry
${cas.version}
Thank you all.
Pada Kamis, 21 Maret 2019
Fahmi,
create-drop is used during initial development of a jpa project when database
design might change regularly. Once database is set, then it gets changed to
update. There is a create option but it will result in errors if the database
already exists. create can be used once and then
Sorry, i am forget attachment.
Strange, I added a service in service management, saved. But there is no
database. But in service management appear. Where is the new service stored?
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines:
Hello Ray, thank for your reply.
I changed the configuration:
- Adding cas.jdbc.showSql=true to cas.properties and management.properties
- Adding healthQuery to cas.properties and management.properties
- Change ddlAuto to update
- Rebuilding project cas and management
Log showing (*cas.log*)
Fahmi,
ddlAuto should be set to 'none' or 'update'.
You can also set cas.jdbc.showSql=true to see queries in the logs.
There is also a health query healthQuery='select ...'
Are you running CAS and management server on the same tomcat at the same time
or do you shut one down and start the other?
Thanks for your replies.
I added the service via CAS Service Manangement
(https://sso.example.com/cas-management/manage.html), but it was not saved
in the database. Please help review my CAS configuration (in attachment).
Can you help me please. Thank you.
Pada Rabu, 20 Maret 2019 23.01.06
I am assuming you don't have version control enabled.
After you add the service through console, is your service shown in
Management console list? If so it should be in your service registry
database.
I have the same exception you describe if version control is not enabled
but I am still able
Fahmi,
It sounds like the management server is saving the service to another location,
most likely file system since that is default.
Also, make sure that CAS and management server are pointing to the exact same
service registry. Check spelling of your properties.
Ray
On Wed, 2019-03-20 at
Thanks Facundo for your reply. Regarding "cas.serviceRegistry.jpa.ddlAuto =
create-drop" is only temporary, next time, I will change it to *none *or
*update*.
So, when I go to *https://sso.example.com/cas-management* (*successfully*),
*then
I make 1 new registry service*. *I think it will
Hi Fahmi,
We faced the same issue with managment console. In our case, that error
is not related to the database configuration or the saving action itself
but the GIT versioning functionalitiy of management console
link of the Maven war Overlay points to cas 6 gradle overlay for both cas
and cas-management app. Can you please provide the Maven war overlay links?
On Friday, November 2, 2018 at 5:51:00 AM UTC+8, Travis Schmidt wrote:
>
> CAS Management version 5.3.5 has been released:
>
Ok. It does seem odd that to search “Trav**” is needed, but at least it is
something. Thanks for your reply.
From: cas-user@apereo.org On Behalf Of Travis Schmidt
Sent: Wednesday, November 07, 2018 11:00 AM
To: cas-user@apereo.org
Subject: Re: [cas-user] Re: CAS Management v5.3.6 Release
Wildcard searches are what you want:
http://lucene.apache.org/core/7_5_0/queryparser/org/apache/lucene/queryparser/classic/package-summary.html#package.description
Doing a quick test against our registry for my first name, Tra?is works,
Tra*is works. For some reason though to make Trav* work
Is the search functionality limited to "whole word" searches? It would be
nice if the search can find partial words as well.
On Friday, November 2, 2018 at 1:57:01 PM UTC-4, Travis Schmidt wrote:
>
> CAS Management v5.3.6 has been released:
>
] Im Auftrag von vu phung
Gesendet: Mittwoch, 1. August 2018 09:56
An: CAS Community
Betreff: [cas-user] Re: cas-management 5.3 from maven overlay
Me too. Pls help me. thanks
Vào 04:47:01 UTC+7 Thứ Sáu, ngày 06 tháng 7 năm 2018, William E. đã viết:
We've been using cas-management 5.2.x
ANd it works! You guys are awesome... Pizza all round!
On Thursday, May 17, 2018 at 3:18:42 PM UTC-4, Jennifer LaVoie wrote:
>
> So I have followed all the steps here
>
>
> https://dacurry-tns.github.io/deploying-apereo-cas/building_svcmgmt_configure-webapp-properties.html
>
> (awesome site)
>
>
I UNDERSTAND. Ok...trying that now...thanks!
Jen
On Fri, May 18, 2018 at 11:48 AM, Ray Bon wrote:
> Jen,
>
> You will need to install custom certs on both sides (CAS and
> cas-management). The jvm is responsible for certificate processing, tomcat
> only needs to know where it is
Jen,
You will need to install custom certs on both sides (CAS and cas-management).
The jvm is responsible for certificate processing, tomcat only needs to know
where it is to send it to the browser.
sudo keytool -import -file ${certName} -alias ${aliasName} -keystore
Yes. I understand the distinction...I was typing quickly :)
I do get an error in my cas-management log about ssl - but my regular
/cas/login link loads just fine (self signed cert on this particular server)
Caused by: sun.security.validator.ValidatorException: PKIX path building
failed:
Jen,
I think you mean a cas-management error and not 'CAS error'.
Are CAS and cas-management running on the same tomcat?
Logging config for cas-management is in log4j2-management.xml which also
introduces cas-management.log.
Ray
On Thu, 2018-05-17 at 12:55 -0700, Jennifer LaVoie wrote:
Sorry, not cas.log cas-management.log.
If still nothing, try setting cas.log.level to debug in
log4j2-management.xml.
--
DAVID A. CURRY, CISSP
*DIRECTOR OF INFORMATION SECURITY*
INFORMATION TECHNOLOGY
71 FIFTH AVE., 9TH FL., NEW YORK, NY 10003
+1 212 229-5300 x4728 •
nothing helpful in cas.log or catalina.out that I can see
it seems to be CAS error because the leaf is on the tab and above the error
that I posted it says
Cas Service Management
Jen
On Thursday, May 17, 2018 at 3:44:27 PM UTC-4, David Curry wrote:
>
> Haven't seen that one, that I can
Haven't seen that one, that I can recall.
Is that a CAS error (shows in a CAS-branded web page) or a Tomcat error?
Do the logs (cas.log and/or catalina.out) say anything helpful?
--
DAVID A. CURRY, CISSP
*DIRECTOR OF INFORMATION SECURITY*
INFORMATION TECHNOLOGY
71 FIFTH AVE., 9TH FL., NEW
I updated the management.properties file with some ports specifically
defined. And that is now working as expected...
However, I get this
The CAS management webapp is unavailable.
There was an error trying to complete your request. Please notify your
support desk or try again.
On
You have "server.name" instead of "cas.server.name" (oops)
--
DAVID A. CURRY, CISSP
*DIRECTOR OF INFORMATION SECURITY*
INFORMATION TECHNOLOGY
71 FIFTH AVE., 9TH FL., NEW YORK, NY 10003
+1 212 229-5300 x4728 • david.cu...@newschool.edu
[image: The New School]
On Thu, May 17, 2018 at 3:23
Here is my management.properties file
# CAS server that management app will authenticate with
# This server will authenticate for any app (service) and you can login as
casuser/Mellon
server.name: https://cashost
cas.server.prefix: ${cas.server.name}/cas
cas.mgmt.adminRoles[0]=ROLE_ADMIN
Hi,
I was facing the same problem, all write/execute/read rights and ownerships
were correct and tomcat could access all mentioned directories but still
there was an error on startup.
Only one thing worked for me. In cas-management-overlay I've overridded
log4j2.xml
Thanks for the help William - I'll give this all a read, see what I can
come up with. Appreciate it!
On Wednesday, November 22, 2017 at 9:53:46 AM UTC-5, William E. wrote:
>
> Resultant cas management screenshot attached.
> Full disclosure, this is our test CAS 5.1, we haven't deployed to
>
Thank you so much. I tried adding the lines you mentioned in my
cas.properties but still no luck. We've got similar setups the only
dependency I don't have in CAS is below.
org.apereo.cas
cas-server-support-saml-sp-integrations
${cas.version}
On Wednesday, November 22, 2017 at
Nope. In my cas 5.1 pom I only have:
org.apereo.cas
cas-server-webapp${app.server}
${cas.version}
war
runtime
org.apereo.cas
cas-server-support-ldap
${cas.version}
Gotcha. Do you also have these defined in your pom.xml ?
org.apereo.service.persondir
person-directory-api
${person.directory.version}
org.apereo.service.persondir
person-directory-impl
${person.directory.version}
On Tuesday, November 21, 2017 at 10:24:47 PM UTC-5,
1 - 100 of 118 matches
Mail list logo