No GIT or authorization. Also tested it's not moving the file from
/etc/cas-mgmt/metadata
With mgmt.metadata-dir=/etc/cas/saml/sp the service.json file is populated
with that value but the file itself is still in /etc/cas-mgmt/metadata
I have it working now, I just made /etc/cas-mgmt/metadata a
You can set this property to your destination (so you do not have to create a
symlink if you change hosts):
mgmt.metadata-repo-dir=/etc/cas/saml/sp
Ray
On Wed, 2024-01-31 at 11:05 -0800, atilling wrote:
Notice: This message was sent from outside the University of Victoria email
system. Please
Do you have git or authorization workflow enabled?
There are two metadata properties (see line 142
https://github.com/apereo/cas-management/blob/6.6.x/api/cas-mgmt-api-configuration/src/main/java/org/apereo/cas/configuration/CasManagementConfigurationProperties.java
)
private String
Added:
mgmt.metadata-dir=file:/etc/cas/saml/sp/
But when i upload metadata it's still trying to write to
/etc/cas-mgmt/metadata/
On Tuesday, January 30, 2024 at 2:57:06 PM UTC-5 Ray Bon wrote:
> Try
> mgmt.metadata-dir=
>
>
> Ray
>
> On Tue, 2024-01-30 at 09:36 -0800, atilling wrote:
>
>
Try
mgmt.metadata-dir=
Ray
On Tue, 2024-01-30 at 09:36 -0800, atilling wrote:
Notice: This message was sent from outside the University of Victoria email
system. Please be cautious with links and sensitive information.
Further clarification after some experimentation. This only applies to
Further clarification after some experimentation. This only applies to
metadata you are uploading via the service manager.
The service manager places the file in /etc/cas-mgmt/metadata
BUT
if build the service.json file with
metadataLocation: file://etc/cas/metadata/service.xml
Sort of figured this out, at least the error part.
cas-management is trying to put metadata in /etc/cas-mgmt/metadata which
didn't exist
What property for cas-management sets this?
cas I'm using /etc/cas/saml/sp - need the management to use the same path.
On Tuesday, January 30, 2024 at
