Hi Mark,
It’s because the cert is wildcard for our domain it is breaking going to the
localhost for SOLR. With SOLR setup for localhost only, it got grumpy. I’ve
found an easy way to work around it now. I hope to get apache httpd working on
it in the future.
Jake
--
Jake Cameron, BCS(UNB)
I am setting up a DSpace 6.x dedicated server for the first time and I am
looking for any clues or wisdom from those who have walked this path before.
I have been reading through the installation docs and there are several
choices to be made. We are going to build on Ubuntu 18.04 in a
On Monday, November 5, 2018 at 6:11:29 PM UTC-5, jacob.cameron wrote:
>
> Can I have SOLR secured under a wildcard SSL certificate? I’ve installed
> our cert and forced HTTPS I’m tomcat, but SOLR keeps giving a 302 error now
> and when I browse it it tells me that it’s an invalid cert. I haven’t
Hi.
I don't know if this is the right place to ask about this. If not, I
apologize.
Some time ago I've been asked to implement an instance of DSpace to hold
some multimedia artefacts related to a project. After some discussion on
how to build a communities+collections structure, I created it
Hi Jake,
in Tomcat 8 a rewrite is possible.
In the context in server.xml define
Add a rewrite.config to the path of e.g.
[tomcat-path]/xmlui/WEB-INF/rewrite.config with this contents
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{HTTP_HOST}$1 [R=301,L]
and restart tomcat.
Or
Hi,
There is a ticket for this issue:
https://jira.duraspace.org/browse/DS-3994
I have tested the suggested solution which works fine with our DSpace 6.3
installation.
The check for the colon character as a separator is for when you import the
authority value, such as an ORCID ID.
Example
Hello Sean,
At our repo, https://digital.cic.gba.gob.ar/, we have the same issue as
well. Metadata import fails to parse Authority keys.
I did some debugging and apparently the error is here:
MetadataImport#isAuthorityControlledField()
We don’t want SOLR available publically, and it is secured only to the
localhost. However, when I forced HTTPS our DSpace instance in Tomcat, it
started causing the 302 errors with SOLR. I guess I’m going to have to install
Apache httpd or nginx to handle the certificate. I was hoping to get
Hi Tomas
After downloaded package from https://github.com/DSpace/DSpace/releases Our
dspace has been working fine
Regard
Avinash
From: dspace-tech@googlegroups.com [mailto:dspace-tech@googlegroups.com] On
Behalf Of Tomas Berzinas
Sent: 05 November 2018 12:57
To:
Hi Paul, thanks for answering
but if i don´t setup this collection, after submission process, dspace take
the DEFAULT Workflow.
The Default workflow is assigned the carousel type workflow
Kind regards
the default workfloww is assigned the carousel type
El martes, 6 de noviembre de 2018,
Dear Tim & others,
let me pick up on this issue once again.
I've reimplemented our submission interface using
swordv2-server.expose-communities = true
in local.cfg
This allows to retrieve the bibliography hierarchy level by level and
makes the usage of /rest/hierarchy dispensable for us. It
Dear Jacob,
Is there any reason you need Solr available publicly? It is recommended
that Solr run on localhost and the DSpace applications communicate with it
directly, ie at http://localhost:8080/solr. The Solr application is not
secured and should, under most circumstances, never be exposed
12 matches
Mail list logo
