Am I missing something or there is no way to automatically add new users
(created with OIDC Authentication) to a group ?
Thank you
G
On Monday, March 20, 2023 at 3:10:07 PM UTC-6 Gabriela wrote:
> Hello,
>
> We successfully enabled the OIDC Authentication but I do not see a way to
>
Hello,
We successfully enabled the OIDC Authentication but I do not see a way to
automatically assign new accounts created with OIDC Authentication to a
group.
Gabriela
--
All messages to this mailing list should adhere to the Code of Conduct:
hi , i wanted to configure a handle server on my dspace 7.4 , so i went to
consult the documentation
https://wiki.lyrasis.org/display/DSDOC7x/Handle.Net+Registry+Support
Within the first section, to locate the handle server on the same dspace
machine, use the first command, that is:
We have been notified by campus network authorities that our dspace server
is vulnerable because it is running outdated versions of jQuery. We are in
the process of creating a new dspace 7 server to replace this server, but
that will not happen in the short time that we have been given to fix
Documented the solution on this issue i created on github recently:
https://github.com/DSpace/DSpace/issues/8693
Em seg., 20 de mar. de 2023 às 14:47, Douglas Eder Uno Silva <
deusi...@uefs.br> escreveu:
> Hi Mo!
>
> Man, it worked! Thanks a lot again for the help!
>
> The problem is about the
Hi,
If the default settings in DSpace are not working well for you, it is
likely that you may want to customize the Solr configuration to better
index Chinese. See the tips in this older
post: https://groups.google.com/g/dspace-tech/c/ASAvSlWLJQo/m/U84oIEy9BQAJ
Tim
On Saturday, March 18,
Hi Agustina,
If you are sure it's not a CORS policy error, then I'd recommend checking
the backend logs. That "500 (Internal Server Error)" might also be logged
in dspace.log or tomcat logs. If so, there may be more information there to
help out. If it's reproducible semi-easily, you could
Hi Mo!
Man, it worked! Thanks a lot again for the help!
The problem is about the flag *$query_string* i used after the
*$request_uri* on *proxy_pass* in the location for the backend. I use this
on other applications that I deploy but it seems that for Java/Tomcat works
differently.
When I set
Many thanks for clarifying this @Sean. Since this is a key feature for my
deployment, I will have to postpone the transition to 7.x and follow
closely these bug reports.
Kind regards
Milos
понедељак, 20. март 2023. у 16:44:23 UTC+1 Sean Kalynuk је написао/ла:
> Hi Milos,
>
>
>
> I think it
You most welcome. You could've used Let's Encrypt or the self-signed certs,
doing so will save you some extra work at a later time if your current
implementation involve ingesting items or anything relies on the DSpace
naming. What I mean by that is you might need to replace
It worked!
thank you very much, I changed the ip to 0.0.0.0 in the .json of the
front-end and it worked
El lunes, 20 de marzo de 2023 a las 8:44:12 UTC-6, Mohammad S. AlMutairi
escribió:
> Correction: port: 4000 should be port: 80
>
> On Monday, March 20, 2023 at 5:42:33 PM UTC+3 Mohammad S.
Hi Milos,
I think it is this bug:
https://github.com/DSpace/dspace-angular/issues/1758
--
Sean
From: dspace-tech@googlegroups.com on behalf of
Milos Ivanovic
Date: Sunday, March 19, 2023 at 3:11 PM
To: DSpace Technical Support
Subject: Re: [dspace-tech] ORCID autohority in DSpac 7.5
Dear all,I would like to ask for help..
I have dspace 7.5 installed successfully in Ubuntu 22.04 LTS but how do I
make it accessible in the local area network (192.168.xx.x )instead of
localhost? kindly advise in a clear way how to do that...
Thank in advance
i
Hi,
You appear to be looking at the DSpace *backend* directory. DSpace has a
frontend and a backend. To modify the frontend's settings/theme you must
locate the directory where you installed the frontend. It should have the
setup as described
in
Hi Raja,
Backend/frontend version requirements for 7.5 are listed
at https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace
The versions you listed above all look fine.
Tim
On Thursday, March 16, 2023 at 7:25:27 AM UTC-5 raja...@gmail.com wrote:
> Hi Team,
>
> Could you please share
Hi Jan,
DSpace 7 doesn't provide an option to have a Bitstream (File) download link
based on an Item's assigned Handle. Instead, download links *are*
persistent and public, but are based on the UUID of the Bitstream/file like
this:
https://[dspace.url]/bitstreams/[uuid-of-bitstream]/download
Hi Milos,
Unfortunately, the error messages displayed in the UI aren't enough
information to debug the issue. You'd need to locate the underlying
exceptions behind those error messages, as those will provide more clues as
to whether the problem is one of your configs or maybe something else
Correction: port: 4000 should be port: 80
On Monday, March 20, 2023 at 5:42:33 PM UTC+3 Mohammad S. AlMutairi wrote:
> Good Morning,
>
> I think the public access to your server is natted from the public IP
> (150.136.129.10) to the server private IP address (unknown). You have to
> find out
Hi.
I was migrating my database from dspace 4 to dspace 7, I had some errors
that I was able to fix in the migration.
but at the moment of entering through the ip it gave the following error.
I leave attached image.
greetings.
[image: Screenshot_1.png]
--
All messages to this mailing list
Good Morning,
I think the public access to your server is natted from the public IP
(150.136.129.10) to the server private IP address (unknown). You have to
find out the frontend server private IP address and use it or as an
alternative you can use 0.0.0.0 instead to have the service run on
Hi.
I was migrating my database from dspace 4 to dspace 7, I had some errors
that I was able to fix in the migration.
but at the moment of entering through the ip it gave the following error.
I leave attached image.
greetings.
--
All messages to this mailing list should adhere to the Code
also add that the front end log shows me this error
[image: Captura de pantalla 2023-03-20 075206.png]
El lunes, 20 de marzo de 2023 a las 7:29:09 UTC-6, Jorge Alberto Bonilla
Castaneda escribió:
> good morning
>
> Well, that configuration works for me when we talk about a local network,
>
good morning
Well, that configuration works for me when we talk about a local network,
but when that configuration is already used in servers hosted in the cloud,
the front-end stops working
verify that the required addresses are publicly accessible:
http://150.136.129.10:8983/solr/#/
Hi Matías,
Looks like you've hit this common installation
issue
Hello!
I have a 7.5 server updated from 5.4.
The database update process finished OK.
But the index-discovery fails.
2023-03-20 09:24:03.611 INFO index-discovery - 4 @ The script has started
2023-03-20 09:24:03.611 INFO index-discovery - 4 @ Updating Index
2023-03-20 09:24:43.049 ERROR
25 matches
Mail list logo
