-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ CAS ] Error missing /etc/cas/saml #133
Comments
Is your datadir uptodate ? especially these 2 lines: |
oh, or maybe the cas.properties is templated into the ansible playbook ... |
it is templated indeeed, but @landryb updated it last week: https://github.com/georchestra/ansible/blame/master/roles/georchestra/templates/cas/cas.properties.j2 |
I have the last version of playbook, I see the templating, but in the final datadir /etc/georchestra/cas/config neither cas.properties or log4j2.xml are updated. Could they come from the debian package ? |
the playbook deploys the datadir and the templates after installing the debian package, so if you run as for the empty |
i was wrong in my previous comment and misread yours.. after checking, the datadir is deployed/customized before deploying debian packages, which apparently overrides the customizations done by the playbook since config files are also shipped by the debian package. That is.. a definitely strange behaviour, because by default when left unattended/without user interaction (ie when run from ansible), dpkg shouldn't override already present files... |
It gets back to one point brought during the codesprint: what about dropping the default |
can repro on a test instance, after removing
installing
has overriden the customizations. iirc this doesnt happen with other packages... definitely strange.
|
the way ansible installs the packages via apt, it should use or i'm not reading https://dyn.manpages.debian.org/bookworm/dpkg/dpkg.1.en.html#force~2 right... |
@pierrejego can you check what happens if you add:
|
that or |
Maybe it would deserve a new package, then (I'd expect that in debian conventions, you would need to have |
When deploying playbook ( master ) on new Debian 12 via vagrant, proxycas webapp won't start cas-server application because a folder is missing.
I could not find any configuration link to /etc/cas/saml in datadir but in cas-server docs there is some touch :
https://apereo.github.io/cas/7.0.x/installation/Configuring-SAML2-DynamicMetadata.html
Create empty folder /etc/cas/sam fix to problem but might not be the answer.
The text was updated successfully, but these errors were encountered: