[dspace-tech] doi filtering problems with identifier service - dspace 7.5

[Romy Forrer]

Hi there

We have recently installed dspace 7.5 on RHEL 8 server.
I have added a couple of additional conditions and statements to the 
example doi-filter in item-filters.xml and set up 
identifiers.submission.filter.install = doi-filter in local.cfg
and the DOIIdentifierProvider with the filter property (uncommented the 
existing example in indentifier-service.xml).

I've tested my filter via the TestLogicRunner successfully 
e.g. of output below

[dspace]$ [dspace]/bin/dspace dsrun 
org.dspace.content.logic.TestLogicRunner -f doi-filter -i 123456789/105577
Starting impl of main() test spring logic item filter
true

but for some reason on item install/archive the identifier service is 
always evaluating items as false according to the dspace log and no items 
are added to the doi table:

e.g.

2023-06-28 17:55:49,566 WARN  4d31b166-1d54-4149-b159-6a74a9e84b64 
f21e0307-bfd2-42f8-9281-53c7dd41663f 
org.dspace.identifier.IdentifierServiceImpl @ Identifier not registered 
(inapplicable): Item 123456789/105577 was evaluated as 'false' by the item 
filter, not minting
I've tried removing the identifiers.submission.filter.install = 
doi-filter config line and only having the filter referenced in 
identifier-service.xml DOIIdentifierProvider section and also tried the 
opposite (removing the filter property line in DOIIdentifierProvider). Have 
tried alternatively uncommenting both seemingly identical versions of the 
DOIIdentifierProvider in the spring config file but both give the same 
result - all items rejected by the filtering.
Removing both the filtering parameters, all archived items go in to the doi 
table with status of 7 as expected.

I'm a bit stumped - it feels like the IdentifierServiceImpl isn't finding 
and using the doi-filter in item-filters.xml whereas the test logic runner 
is. The log output doesn't give me details of what item filter the 
identifier service is actually evaluating (if any - the same error message 
seems to be used in various bits of the else if loop in the code). Be 
grateful for any advice on this as we would love to get the doi filtering 
working. 
If it makes any difference we have not set identifiers.submission.register 
to true as we plan to just use the register doi button to do adhoc minting 
of items still in the submission process. The register doi button works 
well :) - many thanks to the developers for that.

Kind Regards,

Romy
Romy Forrer
Library Systems Co-ordinator
University of Canterbury (NZ)

-- 
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/7bd98247-b783-42e3-a0f8-fa39aed4e4c2n%40googlegroups.com.

[dspace-tech] Crash of metadata-import into workflow

[Marwa Saada]

Hello dspace team,
We had a problem with metadata import after switching to dspace 7, on the 
productive server the import only works if the Excel file has a certain 
number of items (was 8) otherwise the process craches and no items will end 
up in the workflow, also there is no error message or clear exception. 
With debugging we found that the process stops in the EventServiceImpl 
class, and when we increased the values of pool configuration keys ( 
maxTotalPerKey, maxIdlePerKey, maxTotal ) there, the import continued 
successfully with a file up to 25 items. 

Are there any consequences that these keys have other values than the one 
already initialized in Dspace (100, 5, 100).
I would appreciate an explanation

Marwa

-- 
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/e6d8e78f-6863-4036-848b-8dd3c633059en%40googlegroups.com.

[dspace-tech] Register for DSpace 7.6 Live Question and Answer Session July 19, 2023

[DSpace Technical Support]

Register for DSpace 7.6 Live Question and Answer Session July 19, 2023 

When: July 19, 2023 at 14:00-15:30 UTC (use this tool to convert your local 
time to UTC time ) 

Where: Register via the Lyrasis Website 


In this live event, DSpace Technical Lead Tim Donohue and DSpace Program 
Coordinator Natalie Baur will host a DSpace 7.6 question and answer 
session. This free webinar will review the latest DSpace release and answer 
community questions about DSpace 7.6.  

Please add questions that you would like to be answered during the event on 
the following Q document: 
 https://tinyurl.com/dspace76QA

A recording of this webinar will be made available to registrants after the 
event. 

 

Inscripciones abiertas para sesión en vivo “DSpace 7.6: Preguntas y 
Respuestas”  

Fecha: 19 de julio, 2023 a las 14:00-15:30 UTC (conviérte el horario UTC a 
su hora local)  

Registro: 
Inscripciones
 
abiertas aquí  


En este evento, Tim Donahue (liderazgo técnico) y Natalie Baur 
(coordinadora del programa) organizan un evento para dar respuestas a las 
preguntas desde la comunidad de DSpace sobre aspectos técnicos del nuevo 
lanzamiento de DSpace 7.6. Este evento será grabado y contará con la 
interpretación simultánea al español.  

Se puede agregar sus preguntas al documento compartido: 
https://tinyurl.com/dspace76QA

-- 
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/8e7225b1-d1ad-4e81-8b93-8e91fe32bd05n%40googlegroups.com.

Re: [dspace-tech] SMTP over TLS Failed

[Douglas Eder Uno Silva]

For me too!

Thanks Cristhian Andres Rey Casadiego !

Em sábado, 12 de março de 2022 às 10:32:30 UTC-3, Chalew Tesfaye escreveu:

> Cristhian's method worked for me too.!
> Thank you
>
> On Thursday, December 9, 2021 at 6:52:58 PM UTC+3 redu@gmail.com 
> wrote:
>
>> Cristhian's method worked for me too.!
>> Thanks for the help.
>>
>> Regards,
>>
>> El viernes, 14 de mayo de 2021 a las 19:03:37 UTC-6, Agboola Raphael 
>> escribió:
>>
>>> Yes,  Cristhian Rey method works for me.
>>> Thanks
>>>
>>> On Thursday, May 6, 2021 at 1:04:42 AM UTC+1 crisan...@gmail.com wrote:
>>>
 Hi everybody I had the same issue in debian and fixed it adding this in 
 dspace.conf:

 mail.extraproperties = mail.smtp.socketFactory.port=587, \

 mail.smtp.starttls.enable=true, \

 mail.smtp.starttls.required=true, \

 mail.smtp.ssl.protocols=TLSv1.2


 Best Regards,


 Cristhian Rey

 Colombia

 El miércoles, 17 de marzo de 2021 a las 14:08:24 UTC-5, 
 gonza...@gmail.com escribió:

> Just adding some info I've found troubleshooting the same error 
> (javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol 
> is 
> disabled or cipher suites are inappropriate)
>
> Running DSpace on Centos8 could require that command, depending on 
> your mail provider, as far as TLS 1.0 and 1.1 are deprecated and a legacy 
> mode is needed. 
>
> This solved the issue to me, using SMTPS under TLS on port 465
>
>
> https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/considerations_in_adopting_rhel_8/security_considerations-in-adopting-rhel-8#tls-v10-v11_security
>
>
> El Wednesday, December 9, 2020 a la(s) 5:39:39 PM UTC-3, 
> hbla...@gmail.com escribió:
>
>> Hi for all, 
>> Today I finally found a solution, the problem was with the operating 
>> system. execute the following command 
>>
>>  update-crypto-policies --set LEGACY  
>>
>> and after reboot it has worked.
>> Thanks to everyone for your support.
>>
>> El martes, 8 de diciembre de 2020 a la(s) 16:45:42 UTC-5, 
>> jacob.cameron escribió:
>>
>>> That should have said TLS 1.0 and 1.1 support.
>>>
>>>  
>>>
>>>  
>>>
>>> --
>>>
>>> Jake Cameron, BCS(UNB)
>>>
>>> Systems Support Specialist III
>>>
>>> Information Systems and Technical Services University of Lethbridge 
>>> Library
>>>
>>> Phone:(403)329-2756 <(403)%20329-2756>
>>>
>>> This e-mail, including any and all attachments, is only for the use 
>>> of the intended recipient(s) and may contain information that is 
>>> confidential or privileged. If you are not the intended recipient, you 
>>> are 
>>> advised that any dissemination, copying or other use of this e-mail is 
>>> prohibited. Please notify the sender of the error in communication by 
>>> return e-mail and destroy all copies of this e-mail. Thank you.
>>>
>>>  
>>>
>>> *From:* dspac...@googlegroups.com  *On 
>>> Behalf Of *Cameron, Jacob
>>> *Sent:* Tuesday, December 8, 2020 8:54 AM
>>> *To:* Humberto Blanco Castillo ; DSpace 
>>> Technical Support 
>>> *Subject:* RE: [dspace-tech] SMTP over TLS Failed
>>>
>>>  
>>>
>>> Hello Humberto,
>>>
>>>  
>>>
>>> Microsoft has ended TLS 1.0 and TLS 1.2 support for all their mail 
>>> products.  You need to ensure you are using TLS 1.2 or higher on your 
>>> server or the messages will fail.
>>>
>>>  
>>>
>>>  
>>>
>>> --
>>>
>>> Jake Cameron, BCS(UNB)
>>>
>>> Systems Support Specialist III
>>>
>>> Information Systems and Technical Services University of Lethbridge 
>>> Library
>>>
>>> Phone:(403)329-2756 <(403)%20329-2756>
>>>
>>> This e-mail, including any and all attachments, is only for the use 
>>> of the intended recipient(s) and may contain information that is 
>>> confidential or privileged. If you are not the intended recipient, you 
>>> are 
>>> advised that any dissemination, copying or other use of this e-mail is 
>>> prohibited. Please notify the sender of the error in communication by 
>>> return e-mail and destroy all copies of this e-mail. Thank you.
>>>
>>>  
>>>
>>> *From:* dspac...@googlegroups.com  *On 
>>> Behalf Of *Humberto Blanco Castillo
>>> *Sent:* Tuesday, December 8, 2020 8:26 AM
>>> *To:* DSpace Technical Support 
>>> *Subject:* [dspace-tech] SMTP over TLS Failed
>>>
>>>  
>>>
>>> Caution: This email was sent from someone *outside of the 
>>> University of Lethbridge*. Do not click on links or open 
>>> attachments unless you know they are safe. Suspicious emails should be 

Re: [dspace-tech] Re: Shibboleth on DSpace 7.2 won't work for unknown reasons

[Mark H. Wood]

On Thu, Jun 29, 2023 at 03:10:32AM -0700, Matthias Letsch wrote:
> This has at least resulted in the 403 becoming a 401 and DSpace noticing 
> something about the login attempt, which I consider positive progress.
> 
> However, DSpace now complains in the logs that it cannot find the required 
> attributes:
> 
> 2023-06-29 11:58:35,693 ERROR unknown unknown 
> org.dspace.authenticate.ShibAuthentication @ Shibboleth authentication was 
> not able to find a NetId, Email, or Tomcat Remote user for which to 
> indentify a user from.
> 2023-06-29 11:58:35,707 ERROR unknown unknown 
> org.dspace.authenticate.ShibAuthentication @ Unable to register new eperson 
> because we are unable to find an email address along with first and last 
> name for the user.
>   NetId Header: 'SHIB-NETID'='null' (Optional)
>   Email Header: 'SHIB-MAIL'='null'
>   First Name Header: 'SHIB-GIVENNAME'='null'
>   Last Name Header: 'SHIB-SURNAME'='null'
> 2023-06-29 11:58:35,709 INFO  unknown unknown 
> org.dspace.app.rest.security.EPersonRestAuthenticationProvider @ 
> anonymous::failed_login:email=null, result=4
> 2023-06-29 11:58:35,719 ERROR unknown unknown 
> org.dspace.app.rest.security.StatelessLoginFilter @ Authentication failed 
> (status:401)
> org.springframework.security.authentication.BadCredentialsException: Login 
> failed
> 
> So I guess I need to modify the attribute-map.xml accordingly to match the 
> expected attributes under 
> [dspace]/config/modules/authentication-shibboleth.cfg. 
> 
> The documentation at 
> https://wiki.lyrasis.org/display/DSDOC7x/Authentication+Plugins#AuthenticationPlugins-ShibbolethAuthentication
>  
> provides a template for attribute-map with the attributes that seem to 
> match at first glance. 
> 
> But unfortunately that alone does not change anything for us. Do you 
> possibly know more about this?

You need to know the OIDs used by your Shibboleth IDP to label the
attributes that you want.  These may vary from site to site.
attribute-map.xml maps them to names SHIB-NETID and the rest.  If you
don't give the right OIDs, nothing will be mapped into the request.

You also need to know (or set) the request attributes that DSpace
expects.  That's the other side of the mapping.

Here we are using attributePrefix='AJP_' and it works.  We do not set
ShibUseHeaders.  Tomcat will strip the prefix and pass the attributes
through in the Request.  But Tomcat must be configured to accept more
than the default set of attributes:  the AJP connector must have
'allowedRequestAttributesPattern='SHIB-.*' to let them through.

-- 
Mark H. Wood
Lead Technology Analyst

University Library
Indiana University - Purdue University Indianapolis
755 W. Michigan Street
Indianapolis, IN 46202
317-274-0749
www.ulib.iupui.edu

-- 
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/ZJ2Nwy4fJH_UE1jD%40IUPUI.Edu.


signature.asc
Description: PGP signature

[dspace-tech] Crear un Item en dspace 7 usando /api/core/items y php

[Carlos De Santis]

Alguien tiene información al respecto

-- 
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/9c1ba32a-1d37-43d2-b177-48848973bc73n%40googlegroups.com.

[dspace-tech] Re: Shibboleth on DSpace 7.2 won't work for unknown reasons

[Matthias Letsch]

Hallo Matti,

thank you very much!

This has at least resulted in the 403 becoming a 401 and DSpace noticing 
something about the login attempt, which I consider positive progress.

However, DSpace now complains in the logs that it cannot find the required 
attributes:

2023-06-29 11:58:35,693 ERROR unknown unknown 
org.dspace.authenticate.ShibAuthentication @ Shibboleth authentication was 
not able to find a NetId, Email, or Tomcat Remote user for which to 
indentify a user from.
2023-06-29 11:58:35,707 ERROR unknown unknown 
org.dspace.authenticate.ShibAuthentication @ Unable to register new eperson 
because we are unable to find an email address along with first and last 
name for the user.
  NetId Header: 'SHIB-NETID'='null' (Optional)
  Email Header: 'SHIB-MAIL'='null'
  First Name Header: 'SHIB-GIVENNAME'='null'
  Last Name Header: 'SHIB-SURNAME'='null'
2023-06-29 11:58:35,709 INFO  unknown unknown 
org.dspace.app.rest.security.EPersonRestAuthenticationProvider @ 
anonymous::failed_login:email=null, result=4
2023-06-29 11:58:35,719 ERROR unknown unknown 
org.dspace.app.rest.security.StatelessLoginFilter @ Authentication failed 
(status:401)
org.springframework.security.authentication.BadCredentialsException: Login 
failed

So I guess I need to modify the attribute-map.xml accordingly to match the 
expected attributes under 
[dspace]/config/modules/authentication-shibboleth.cfg. 

The documentation at 
https://wiki.lyrasis.org/display/DSDOC7x/Authentication+Plugins#AuthenticationPlugins-ShibbolethAuthentication
 
provides a template for attribute-map with the attributes that seem to 
match at first glance. 

But unfortunately that alone does not change anything for us. Do you 
possibly know more about this?

Thanks again and best regards
Matthias
Matti Yrjölä schrieb am Mittwoch, 28. Juni 2023 um 18:03:53 UTC+2:

> Hi,
>
> Do you have the attribute attributePrefix="AJP_" set in your 
> ApplicationDefaults (in shibboleth2.xml)?
> I think we had similar problem with that setting as we are using that with 
> older DSpace. 
> Removing the AJP_ prefix and also adding "ShibUseHeaders On" in  
>  and   "/server/api/authn/login"> solved this issue.
>
> There was some discussion in:
> https://github.com/DSpace/DSpace/pull/2651#issuecomment-604902452 
> and
> DSpace 7 Shibboleth Configuration - DSpace - LYRASIS Wiki 
>  
> " The AJP proxy only works (Ben Bosman 
> ) if shibboleth2.xml 
> *doesn't* contain the attribute *attributePrefix="AJP_"* in 
> the ApplicationDefaults. "
>
> Best regards,
> Matti
>
> On Tuesday, June 27, 2023 at 4:33:20 PM UTC+3 Matthias Letsch wrote:
>
>> Hello,
>>
>> for some reason we won't get Shibboleth working.
>>
>> We have a test IdP and test credentials to log in, but something is still 
>> not working. Our colleague from the IDP side says that the communication 
>> between the Shib Daemon on our Server and the Shibboleth IdP is working and 
>> therefore the tasks from his side are finished for now. But he suspects 
>> that Dspace is not communicating properly with shibd and that we have to 
>> change some configurations.
>>
>> As of now I am able get to the Shibboleth login page and to log in with 
>> the test credentials and to accept the metadata usage, but then there is a 
>> HTTP Status 403 report:
>>
>> HTTP Status 403 – Forbidden
>> --
>>
>> *Type* Status Report
>>
>> *Description* The server understood the request but refuses to authorize 
>> it.
>> --
>> Apache Tomcat/9.0.31 (Debian)
>>
>> Has anyone had this problem and knows how to solve it?
>>
>> Thank you and kind regards
>> Matthias
>>
>

-- 
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/a3a7e624-986c-4b41-8811-0d8535416cd1n%40googlegroups.com.