;
> On Tue, Oct 10, 2017 at 10:57 AM, Doug Campbell <
> wdouglascampb...@gmail.com> wrote:
>
>> Christian,
>>
>>
>>
>> I believe I ran into this too at one point. If I remember correctly you
>> just need to add the following dependency to your CAS overlay p
*From:*cas-user@apereo.org <mailto:cas-user@apereo.org>
[mailto:cas-user@apereo.org <mailto:cas-user@apereo.org>] *On
Behalf Of *Christian Axel Schmidt Dick
*Sent:* Tuesday, October 10, 2017 4:10 PM
*To:* CAS Community
*Subject:* [cas-user] Avoid default services recr
I think the build process just grabs the
>> two files you mention from the CAS source.
>>
>>
>>
>> Doug
>>
>>
>>
>> *From:* cas-...@apereo.org [mailto:cas-...@apereo.org
>> ] *On Behalf Of *Christian Axel Schmidt Dick
>> *Sent:* Tues
as-user@apereo.org] *On Behalf Of
> *Christian
> Axel Schmidt Dick
> *Sent:* Tuesday, October 10, 2017 4:10 PM
> *To:* CAS Community
> *Subject:* [cas-user] Avoid default services recreation cas overlay
>
>
>
> Hi there, It might be a noob question but it is something tha
-user] Avoid default services recreation cas overlay
Hi there, It might be a noob question but it is something that should be easy
to avoid, that is driving me mad. I am using the war overlay 5.1.4, and have
docker-ized it. But everytime I start the container, 2 files inside the
services
Hello, you need your own configurations, which were not found.
Try to find the right parameters for 5.1.4 eg (works in 5.2.0-x):
cas.serviceRegistry.json.location: file:///etc/cas/services
We also had other minor problems with 5.1.x and switched directly to
5.2.0-rc2.
Regards, Gena
Hi there, It might be a noob question but it is something that should be
easy to avoid, that is driving me mad. I am using the war overlay 5.1.4,
and have docker-ized it. But everytime I start the container, 2 files
inside the services folder get created 'Apereo-1002.json' and