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 symbolic link to /etc/cas/saml/sp and with the mgmt.metadata-dir the service files are populated correctly. It would make more sense for the service manager to put the file in the /etc/cas/saml/sp location but this is a viable work around for now. On Wednesday, January 31, 2024 at 1:56:37 PM UTC-5 Ray Bon wrote: > 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 metadataRepoDir = "/etc/cas-mgmt/metadata"; > private String metadataDir = "/etc/cas/metadata"; > > The repo one should be a temporary location for using git or perhaps an > authorization step. > Once changes are accepted, cas-management should move the file to > metadataDir. > > Ray > > On Wed, 2024-01-31 at 09:44 -0800, atilling wrote: > > Notice: This message was sent from outside the University of Victoria > email system. Please be cautious with links and sensitive information. > > 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: > > 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 > 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 > > cas.service-registry.json.location=file:/etc/cas/services seems to be > working in cas-management > but > cas.samlMetadataUi.resources=file:/etc/cas/saml/sp/ seems to be ignored > unless there is a different parameter for where metadata should be stored > by default. > On Tuesday, January 30, 2024 at 11:53:50 AM UTC-5 atilling wrote: > > 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 11:02:27 AM UTC-5 atilling wrote: > > I'm using cas service manager 6.6.3 with CAS 6.6.13 attempting to add a > new sp. When I select upload metadata I get a response that the service is > already registered but I have no services on the server except the service > manager itself. > > > > > > -- - Website: https://apereo.github.io/cas - Gitter Chatroom: https://gitter.im/apereo/cas - List Guidelines: https://goo.gl/1VRrw7 - Contributions: https://goo.gl/mh7qDG --- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/88d382aa-5bb8-4aa0-b2d9-040fd5a471cdn%40apereo.org.
