[dspace-tech] users cannot edit bitstreams of their workspace item

[Franziska Rapp]

Hi,

We have cases where users can no longer edit the bitstream(s) of their
workspace item. They can edit the metadata, though.
The error is: "Authorization denied for action REMOVE on BUNDLE:x by
user xx."

When they initially upload their item, they do not have that problem. It
occurs with items that were submitted and then rejected.

This happened shortly after we introduced community admins and modified
the section in dspace.cfg where the rights for delegate admins are
defined. One of the changes was to restrict the create/delete bitstreams
permissions for the community admin, collection admin and item admin. We
made these changes because in our repository community admins should not
create/delete bitstreams of archived items.

# ITEM ADMIN

core.authorization.item-admin.policies = false

# also bundle...

core.authorization.item-admin.create-bitstream = false

core.authorization.item-admin.delete-bitstream = false

core.authorization.item-admin.cc-license = false

Any help would be much appreciated.

Best regards
Franziska


-- 
Franziska Rapp
Communication and Information Center (kiz)
Ulm University

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/0df6f6a2-3d67-6e16-d38d-6a4f442b8fea%40uni-ulm.de.

Re: [dspace-tech] DSpace 7: 'Invalid email or password'

[Sean Carte]

Thanks, Tim. I did try using the IP address everywhere, and that didn't
work. But, as you point out, that would be because I wasn't using HTTPS.

As you also point out, it's right there in the instructions: 'Running the
DSpace Backend on HTTP & port 8080 is only usable for local development
environments (where you are running the UI and REST API from the same
machine, and only accessing them via localhost URLs).'

I must have read that a hundred times without taking it in.

I'll try again with the IP addresses and HTTPS.

Sean

On Wed, 18 Aug 2021 at 17:01, Tim Donohue  wrote:

> Hi Sean,
>
> It looks like your environment.prod.ts is using a "localhost" based URL
> for the REST API.  This means it will attempt to access your REST API on
> the *same machine *where you are running your web browser.
>
> In other words, a localhost URL for the REST API is only valid if you are
> in a development environment...where both the UI and REST API are running
> on your local machine & you are only accessing both via localhost URLs from
> that same machine.
>
> Since it sounds like you are accessing your REST API via a public IP
> address (10.4.36.43), you should be using that same public URL/IP address
> in your "rest" settings for environment.prod.ts.  Keep in mind, your REST
> API also MUST be running HTTPS if you plan to run it on a non-localhost
> URL.
>
> See the various "Common Installation Issues" here:
> https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-CommonInstallationIssues
>
> Also, see step 16 of the Backend Installation instructions:
> https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-BackendInstallation
>
> Good luck!
> Tim
>
>
> --
> *From:* dspace-tech@googlegroups.com  on
> behalf of Sean Carte 
> *Sent:* Tuesday, August 17, 2021 8:21 AM
> *To:* DSpace Technical Support 
> *Subject:* [dspace-tech] DSpace 7: 'Invalid email or password'
>
> After installing DSpace 7, I created an administrator account, but am
> unable to log in using those credentials; I get the error: 'invalid email
> or password'.
>
> I am able to use those credentials to log into the HAL Browser, however.
>
> I'm using a VM on a remote server with the following URLs:
>
> http://10.4.36.43:8080/server/
> http://10.4.36.43
>
> I have Nginx configured to proxy port 4000.
>
> I checked the Network tab of Firefox's Dev Tools, and saw CORS Failed
> errors, and the DSpace installation documentation,
>
>- By default, the DSpace REST API / Backend will only trust the
>application at dspace.ui.url.  Therefore, you should first verify that
>your dspace.ui.url setting (in your local.cfg) exactly matches the
>*primary* *URL* of your User Interface (i.e. the URL you see in the
>browser).  This must be an exact match: mode (http vs https), domain, port,
>and subpath(s) all must match.
>- If you need to trust *additional* client applications / URLs, those
>MUST be added to the rest.cors.allowed-origins configuration. See REST
>API  for details on
>this configuration.
>
> So I added these to the foot of my local.cfg and restarted tomcat:
>
> rest.cors.allow-origins = ${dspace.ui.url}
> rest.cors.allow-origins = http://localhost
> rest.cors.allow-origins = http://10.4.36.43:4000
> rest.cors.allow-origins = http://10.4.36.43
> rest.cors.allow-origins = http://localhost:8080
> rest.cors.allow-origins = localhost:8080
>
> But that doesn't seem to have helped:
>
> [image: Selection_021.png]
> These are my configurations:
>
> src/environments/environment.prod.ts:
> export const environment = {
>   ui: {
>   ssl: false,
>   host: 'localhost',
>   port: 4000,
>   nameSpace: '/'
>   },
>   rest: {
>   ssl: false,
>   host: 'localhost',
>   port: 8080,
>   nameSpace: '/server'
>   }
> };
>
> /dspace/config/local.cfg:
> dspace.dir=/dspace
> dspace.server.url = http://localhost:8080/server
> dspace.ui.url = http://localhost:4000
>
> /etc/nginx/sites-enabled/default:
> location / {
> proxy_pass  http://localhost:4000;
> proxy_http_version 1.1;
> proxy_set_header Upgrade $http_upgrade;
> proxy_set_header Connection ‘upgrade’;
> proxy_set_header Host $host;
> proxy_cache_bypass $http_upgrade;
> proxy_set_header X-Real-IP $remote_addr;
> proxy_set_header HOST $http_host;
> proxy_set_header X-NginX-Proxy true;
> proxy_set_header X-Forwarded-Proto $scheme;
> }
>
> Any ideas where I've gone wrong?
>
> Sean
>
> --
> All messages to this mailing list should adhere to the Code of Conduct:
> https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
> ---
> You received this message because you are subscribed to the Google Groups
> "DSpace Technical Support" group.
> To unsubscribe from this group

Re: [dspace-tech] DSpace 7 REST API

[Kosmas Kaifel]

Hi Tim


thank you very match for the answer.

I known thispage about the REST Contract, but  I do not understand this
how can I create a
DSPACE-XSRF-COOKIE  befor I send the POST command.

Can you give me perhaps an example with the curl command for creation a
DSPACE-XSRF-COOKIE


curl http://dspace7-test.rz.uni-ulm.de:8080/server/api --data
"user=x...@uni-ulm.de&password=xxx" ..?


Best Regards
Kosmas


Am 18.08.2021 um 17:06 schrieb Tim Donohue:
> Hi Kosmas,
>
> See the REST Contract section on CSRF
> tokens: https://github.com/DSpace/RestContract/blob/main/csrf-tokens.md
> 
>
> Simply put, the CSRF Tokens will be sent to you in a prior GET request
> (and they may be updated at any time, so your client code needs to
> watch for them).  The CSRF token will be sent to the client in a
> DSPACE-XSRF-TOKEN header.
>
> Tim
> 
> *From:* dspace-tech@googlegroups.com  on
> behalf of Kosmas Kaifel 
> *Sent:* Wednesday, August 18, 2021 5:49 AM
> *To:* DSpace Technical Support 
> *Subject:* [dspace-tech] DSpace 7 REST API
>  
> Hello,
>
> how can create / receive a valid CSRF token from the REST API
> for POST connection with the REST API.
>
> Best Regards
> Kosmas
>
> -- 
> +---+
> Universität Ulm
> Kommunikations- und Informationszentrum (kiz)
> Abt. Informationsmedien
> Albert-Einstein-Allee 37
> 89081 Ulm
> Tel.   0731/50-15495
> EMail: kosmas.kai...@uni-ulm.de
> ++
>
> -- 
> All messages to this mailing list should adhere to the Code of
> Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
> 
> ---
> You received this message because you are subscribed to the Google
> Groups "DSpace Technical Support" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to dspace-tech+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/619158f2-f21a-4978-2cb1-21a3656c0b11%40uni-ulm.de
> .

-- 
+---+
Universität Ulm
Kommunikations- und Informationszentrum (kiz)
Abt. Informationsmedien
Albert-Einstein-Allee 37
89081 Ulm
Tel.   0731/50-15495
EMail: kosmas.kai...@uni-ulm.de
++

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/5ffac259-abba-b7e8-5088-1489e25dda8c%40uni-ulm.de.

[dspace-tech] Cannot Upload document to new Item - Upload Failed

[Mathieu Pelletier]

I have been trying to squash this one for days now.  I have both backend 
and frontend servers running on the same machine.  Both are running secure 
via apache2 or Nginx proxy (yes, I tried both).

Here is what I see in the console:
[Error] WebSocket connection to 
'wss://redacted2.ac.za/sockjs-node/673/beoy5t2y/websocket' failed: 
Unexpected response code: 400
[Error] Invalid Host/Origin header
error
error (vendor.js:127553)
(anonymous function) (vendor.js:97762)
(anonymous function) (vendor.js:166322)
(anonymous function) (vendor.js:133298)
(anonymous function) (vendor.js:134016)
forEach
(anonymous function) (vendor.js:134014)
(anonymous function)
(anonymous function) (vendor.js:133214)
(anonymous function) (vendor.js:135331)
(anonymous function) (vendor.js:133214)
(anonymous function) (vendor.js:135276)
(anonymous function) (vendor.js:133214)
(anonymous function) (vendor.js:135755)
(anonymous function)
(anonymous function) (vendor.js:133214)
(anonymous function) (vendor.js:134709)
wrapFn (polyfills.js:13605)
runTask (polyfills.js:12554)
invokeTask (polyfills.js:12867)
invokeTask (polyfills.js:14008)
globalZoneAwareCallback (polyfills.js:14034)
[Error] [WDS] Disconnected!
error
close (vendor.js:127556)
(anonymous function) (vendor.js:97741)
(anonymous function) (vendor.js:133298)
(anonymous function) (vendor.js:134098)
(anonymous function)
runTask (polyfills.js:12554)
invokeTask (polyfills.js:12867)
timer (polyfills.js:14939)

Here is what I have in local.cfg:

##

# SERVER CONFIGURATION   #

##


# DSpace installation directory.

# This is the location where you want to install DSpace.

# Windows note: Please remember to use forward slashes for all paths (e.g. 
C:/dspace)

dspace.dir=/data/dspace


# URL of DSpace backend ('server' webapp). Include port number etc.

# DO NOT end it with '/'.

# This is where REST API and all enabled server modules (OAI-PMH, SWORD,

# SWORDv2, RDF, etc) will respond.

dspace.server.url = https://redacted1.ac.za/server


# URL of DSpace frontend (Angular UI). Include port number etc.

# DO NOT end it with '/'.

# This is used by the backend to provide links in emails, RSS feeds, 
Sitemaps,

# etc.

dspace.ui.url = https://redacted2.ac.za


# Name of the site

dspace.name = Research Commons


# assetstore.dir, look at DSPACE/config/spring/api/bitstore.xml for more 
options

# default is ${dspace.dir}/assetstore, uncomment and modify if you need to 
use a different path

#assetstore.dir = assetstore


# Default language for metadata values

#default.language = en_US


# Solr server/webapp.

# DSpace uses Solr for all search/browse capability (and for usage 
statistics).

# Since DSpace 7, SOLR must be installed as a stand-alone service

solr.server = http://localhost:8983/solr


Here is what I have in environments.prod.ts:

export const environment = {

  // The "ui" section defines where you want Node.js to run/respond. It may 
correspond to your primary URL, but it also may not (if you are running b>

  // In this example, we are setting up our UI to just use localhost, port 
4000.

  // This is a common setup for when you want to use Apache or Nginx to 
handle HTTPS and proxy requests to Node on port 4000

  ui: {

  ssl: false,

  host: 'localhost',

  port: 4000,

  // NOTE: Space is capitalized because 'namespace' is a reserved 
string in TypeScript

  nameSpace: '/'

  },

  // This example is valid if your Backend is publicly available at 
https://api.mydspace.edu/server/

  // The REST settings MUST correspond to the primary URL of the backend. 
Usually, this means they must be kept in sync

  // with the value of "dspace.server.url" in the backend's local.cfg

  rest: {

  ssl: true,

  host: 'redacted1.ac.za',

  port: 443,

  // NOTE: Space is capitalized because 'namespace' is a reserved 
string in TypeScript

  nameSpace: '/server'

  },


themes: [

 {

name: 'mytheme'

 },

],


};


I have everything else working, it seems.  I have branded the site, I have 
created communities and collections, but I can't create items because I 
can't upload anything.  I have tried checking directory ownership and 
permissions in the underlying filesystem, but nothing seems to work.

I would appreciate some help if anyone has a clue as to what is going on.

Many thanks!


-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/e63c965e-fc83-45be-8817-6fd75c78196dn%40googlegroups.com.

[dspace-tech] Re: Metadata updates

[al...@vt.edu]

You might also want to consider the DSpace REST Query Client (available in 
DSpace v6), https://demo.dspace.org/rest/static/reports/query.html and 
documented in https://wiki.lyrasis.org/display/DSDOC6x/REST+API.
On Wednesday, August 18, 2021 at 11:10:09 AM UTC-4 sbu...@oakland.edu wrote:

> Hi DSpace Community,
>
> We are looking for a way to query our metadata (not necessarily in the 
> same collection) for matching values.  For instance, if an LC Subject 
> heading changed, we would want to pull all records with that subject 
> heading, export, update and re-import.  Can anyone suggest a proven tool 
> for this type of matching query?  I'm currently looking at postgres via 
> ODBC, but there is a lot of security configuration required for that (out 
> of my control). 
>
> Any ideas are welcomed!  Thank you in advance!
> Sarah
>
> -- 
>
> Sarah Butash
>
> she / her
>
> Library Systems Analyst, OU Libraries
>
> Kresge Library, Room 227
>
> 100 Library Drive, Rochester, MI  48309-4479
>
> Phone: 248-370-2368 <(248)%20370-2368>
>
>
>
>

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/d334ee0c-f232-4b06-a378-4e33ae358177n%40googlegroups.com.

Re: [dspace-tech] DSpace 7 REST API

['Tim Donohue' via DSpace Technical Support]

Hi Kosmas,

You don't need to send any special request to generate the CSRF token...it's 
generated automatically on your first GET request and sent to you in the 
response.  The request you send doesn't matter.  What matters is that you need 
to watch for an HTTP Header named "DSPACE-XSRF-TOKEN" sent back to you in the 
response.   When that Header is specified in any response, that is your new 
CSRF token.

The value of this "DSPACE-XSRF-TOKEN" header is your assigned CSRF token.  
That's the token you will need to send back in your next POST/PUT/PATCH/DELETE 
request. You must send it back in a different HTTP Header, the "X-XSRF-TOKEN" 
header.

Your code MUST watch for a "DSPACE-XSRF-TOKEN" in every response you receive 
from the DSpace REST API.  When that header is sent to you, that means your 
CSRF token has changed.  Your token may change for a variety of reasons (e.g. 
when you login/logout, when you send an invalid request, or if you appear to be 
coming from a different client or have been idle for some time).

(The DSPACE-XSRF-COOKIE does not need to be used at all by your client. It's 
generated by the REST API and it's an HttpOnly cookie, meaning it cannot be 
read by Javascript.  That cookie is only used by the REST API to validate your 
token...i.e. the token you send in X-XSRF-TOKEN to the REST API must match the 
token in that Cookie.)

Tim


From: Kosmas Kaifel 
Sent: Thursday, August 19, 2021 5:33 AM
To: Tim Donohue ; DSpace Technical Support 

Subject: Re: [dspace-tech] DSpace 7 REST API


Hi Tim


thank you very match for the answer.

I known thispage about the REST Contract, but  I do not understand this how can 
I create a
DSPACE-XSRF-COOKIE  befor I send the POST command.

Can you give me perhaps an example with the curl command for creation a 
DSPACE-XSRF-COOKIE


curl http://dspace7-test.rz.uni-ulm.de:8080/server/api --data 
"user=x...@uni-ulm.de&password=xxx" 
..?


Best Regards
Kosmas


Am 18.08.2021 um 17:06 schrieb Tim Donohue:
Hi Kosmas,

See the REST Contract section on CSRF tokens: 
https://github.com/DSpace/RestContract/blob/main/csrf-tokens.md

Simply put, the CSRF Tokens will be sent to you in a prior GET request (and 
they may be updated at any time, so your client code needs to watch for them).  
The CSRF token will be sent to the client in a DSPACE-XSRF-TOKEN header.

Tim

From: dspace-tech@googlegroups.com 
 on behalf 
of Kosmas Kaifel 
Sent: Wednesday, August 18, 2021 5:49 AM
To: DSpace Technical Support 

Subject: [dspace-tech] DSpace 7 REST API

Hello,

how can create / receive a valid CSRF token from the REST API
for POST connection with the REST API.

Best Regards
Kosmas

--
+---+
Universität Ulm
Kommunikations- und Informationszentrum (kiz)
Abt. Informationsmedien
Albert-Einstein-Allee 37
89081 Ulm
Tel.   0731/50-15495
EMail: kosmas.kai...@uni-ulm.de
++

--
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/619158f2-f21a-4978-2cb1-21a3656c0b11%40uni-ulm.de.

--
+---+
Universität Ulm
Kommunikations- und Informationszentrum (kiz)
Abt. Informationsmedien
Albert-Einstein-Allee 37
89081 Ulm
Tel.   0731/50-15495
EMail: kosmas.kai...@uni-ulm.de
++

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/DM5PR2201MB114845A8B0705EE13051B12BEDC09%40DM5PR2201MB1148.namprd22.prod.outlook.com.

Re: [dspace-tech] Cannot Upload document to new Item - Upload Failed

['Tim Donohue' via DSpace Technical Support]

Hi Mathieu,

If you can authenticate successfully & create other object 
(Communities/Collections), that implies that your main setup is correct​. If 
you had major configuration errors in your local.cfg (on backend) and/or 
environment.prod.ts (on frontend), then you would not be able to authenticate 
at all.

That said, it's not clear (to me) what might be the obvious problem with the 
upload process.  I'd recommend you check for errors in the logs on the backend. 
 Primarily check the dspace.log, but also look in the Apache / Tomcat / Nginx 
logs as well (in case more information can be found there).

The Console error you posted is an odd one, as it's unclear why it'd throw an 
"Unexpected response code: 400, Invalid Host/Origin header".  You also might 
want to look closely at your proxy settings in Nginx googling that error 
brought me to this StackOverflow answer: https://stackoverflow.com/a/48096141   
I admit, I'm not familiar enough with Nginx (I tend to use Apache), so I don't 
know if this could be the result of a bad proxy setting in Nginx.

You also might want to be sure that nothing is blocking X-Forwarded-* headers 
in your Proxy... as it's also possible something like this is happening: 
https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-MyRESTAPIisrunningunderHTTPS,butsomeofits%22link%22URLsareswitchingtoHTTP?

If you figure out the issue, please report back on the fix...it's possible you 
are hitting a Proxy configuration issue that others may also encounter -- in 
which case, I'd like to ensure it is more clearly documented in the Install 
docs.

Tim


From: dspace-tech@googlegroups.com  on behalf of 
Mathieu Pelletier 
Sent: Thursday, August 19, 2021 9:20 AM
To: DSpace Technical Support 
Subject: [dspace-tech] Cannot Upload document to new Item - Upload Failed

I have been trying to squash this one for days now.  I have both backend and 
frontend servers running on the same machine.  Both are running secure via 
apache2 or Nginx proxy (yes, I tried both).

Here is what I see in the console:
[Error] WebSocket connection to 
'wss://redacted2.ac.za/sockjs-node/673/beoy5t2y/websocket' failed: Unexpected 
response code: 400
[Error] Invalid Host/Origin header
error
error (vendor.js:127553)
(anonymous function) (vendor.js:97762)
(anonymous function) (vendor.js:166322)
(anonymous function) (vendor.js:133298)
(anonymous function) (vendor.js:134016)
forEach
(anonymous function) (vendor.js:134014)
(anonymous function)
(anonymous function) (vendor.js:133214)
(anonymous function) (vendor.js:135331)
(anonymous function) (vendor.js:133214)
(anonymous function) (vendor.js:135276)
(anonymous function) (vendor.js:133214)
(anonymous function) (vendor.js:135755)
(anonymous function)
(anonymous function) (vendor.js:133214)
(anonymous function) (vendor.js:134709)
wrapFn (polyfills.js:13605)
runTask (polyfills.js:12554)
invokeTask (polyfills.js:12867)
invokeTask (polyfills.js:14008)
globalZoneAwareCallback (polyfills.js:14034)
[Error] [WDS] Disconnected!
error
close (vendor.js:127556)
(anonymous function) (vendor.js:97741)
(anonymous function) (vendor.js:133298)
(anonymous function) (vendor.js:134098)
(anonymous function)
runTask (polyfills.js:12554)
invokeTask (polyfills.js:12867)
timer (polyfills.js:14939)

Here is what I have in local.cfg:

##

# SERVER CONFIGURATION   #

##


# DSpace installation directory.

# This is the location where you want to install DSpace.

# Windows note: Please remember to use forward slashes for all paths (e.g. 
C:/dspace)

dspace.dir=/data/dspace


# URL of DSpace backend ('server' webapp). Include port number etc.

# DO NOT end it with '/'.

# This is where REST API and all enabled server modules (OAI-PMH, SWORD,

# SWORDv2, RDF, etc) will respond.

dspace.server.url = https://redacted1.ac.za/server


# URL of DSpace frontend (Angular UI). Include port number etc.

# DO NOT end it with '/'.

# This is used by the backend to provide links in emails, RSS feeds, Sitemaps,

# etc.

dspace.ui.url = https://redacted2.ac.za


# Name of the site

dspace.name = Research Commons


# assetstore.dir, look at DSPACE/config/spring/api/bitstore.xml for more options

# default is ${dspace.dir}/assetstore, uncomment and modify if you need to use 
a different path

#assetstore.dir = assetstore


# Default language for metadata values

#default.language = en_US


# Solr server/webapp.

# DSpace uses Solr for all search/browse capability (and for usage statistics).

# Since DSpace 7, SOLR must be installed as a stand-alone service

solr.server = http://localhost:8983/solr


Here is what I have in environments.prod.ts:

export const environment = {

  // The "ui" section defines where you want Node.js to run/respond. It may 
correspond to your primary URL, but it also may not (if you are running b>

  // In this example, we are setting up our UI to just use localhost, port 4000.

  // Th

[dspace-tech] Logout redirect error

[Fitchett, Deborah]

Kia ora all,

DSpace 5.8 XMLUI - Is there somewhere where we can configure the behaviour when 
a user logs out?  We're currently getting a "The page isn't redirecting 
properly" error (and I haven't been paying attention enough to know if this is 
new or old behaviour.)  Looks like a series of 302 code responses when 
requesting /logout so that it just keeps redirecting to itself before realising 
that's getting a bit silly and giving up.

I see there's an old JIRA case DS-3505 which describes very similar 
behaviour/situation but that looks like it got fixed by 5.7 so I'm not sure if 
it's actually the cause of something different is.

Deborah



"The contents of this e-mail (including any attachments) may be confidential 
and/or subject to copyright. Any unauthorised use, distribution, or copying of 
the contents is expressly prohibited. If you have received this e-mail in 
error, please advise the sender by return e-mail or telephone and then delete 
this e-mail together with all attachments from your system."

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/SYCPR01MB5037C90BDB3702E2C6A3A74CC5C19%40SYCPR01MB5037.ausprd01.prod.outlook.com.