[dspace-tech] Handle Server is not resolving new handles created on Dspace 6.2

2019-05-15 Thread Edmilson José Boregas 
Hi folks,

We've just upgraded from Dspace 5 to Dspace 6.2.  

Since last Monday, our handle server is not resolving the new items created 
on Dspace 6.2.   

Only the old ones are being resolved.

 

Take a look:


Older handle: http://hdl.handle.net/10438/13788 è redirected 
to http://bibliotecadigital.fgv.br/dspace/10438/13788 

New handle:  http://hdl.handle.net/10438/12 è not found, but  it exists 
on http://bibliotecadigital.fgv.br/dspace/10438/12

 

Could someone help us to solve this problem?



Edmilson José Boregas

Fundação Getulio Vargas

São Paulo, Brasil

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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/a3bdd5d7-9db1-4bde-9fcb-49d0de6b0cc5%40googlegroups.com.

[dspace-tech] Re: Shibboleth Login Issue DSpace 6.3

2019-05-15 Thread Library Systems 
According to this thread 
,
 
DSpace may not be able to recognize the eperson record as a user.  Possibly 
you could adjust the Service Provider attribute mappings to fix this.

Glenn

On Tuesday, May 14, 2019 at 8:14:14 AM UTC-5, Jeff Stone wrote:
>
> Hello All,
>
> I have followed all the documentation I can to setup shibboleth 
> authentication with Dspace.  The Shibboleth SP is installed, I can see the 
> attributes that I need and when I have logged in, it does create  a eperson 
> record, but when logging in they are hit with a Single Sign Out feature is 
> not implemented.
>
> I have turned on DEBUG and the following is shown :
>
>  DEBUG org.dspace.authenticate.ShibAuthentication @ Updated the eperson's 
> minimal metadata: 
>  Email Header: 'mail' = 'us...@xxx.com ' 
>  First Name Header: 'givenName' = 'x' 
>  Last Name Header: 'givenName' = 'xx'
> 2019-05-14 13:50:53,596 ERROR org.dspace.authenticate.ShibAuthentication @ 
> Unable to successfully authenticate using shibboleth for user because of an 
> exception.
> java.lang.NullPointerException
> at 
> org.dspace.content.DSpaceObjectServiceImpl.match(DSpaceObjectServiceImpl.java:429)
> at 
> org.dspace.content.DSpaceObjectServiceImpl.clearMetadata(DSpaceObjectServiceImpl.java:340)
> at 
> org.dspace.content.DSpaceObjectServiceImpl.setMetadataSingleValue(DSpaceObjectServiceImpl.java:395)
> at 
> org.dspace.eperson.EPersonServiceImpl.setMetadata(EPersonServiceImpl.java:393)
> at 
> org.dspace.authenticate.ShibAuthentication.updateEPerson(ShibAuthentication.java:844)
> at 
> org.dspace.authenticate.ShibAuthentication.authenticate(ShibAuthentication.java:225)
> at 
> org.dspace.authenticate.AuthenticationServiceImpl.authenticateInternal(AuthenticationServiceImpl.java:111)
> at 
> org.dspace.authenticate.AuthenticationServiceImpl.authenticate(AuthenticationServiceImpl.java:81)
> at 
> org.dspace.app.webui.servlet.ShibbolethServlet.doDSGet(ShibbolethServlet.java:69)
> at 
> org.dspace.app.webui.servlet.DSpaceServlet.processRequest(DSpaceServlet.java:126)
> at org.dspace.app.webui.servlet.DSpaceServlet.doGet(DSpaceServlet.java:73)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:635)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:742)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
> at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
> at 
> org.dspace.utils.servlet.DSpaceWebappServletFilter.doFilter(DSpaceWebappServletFilter.java:78)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
> at 
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:198)
> at 
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96)
> at 
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:493)
> at 
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:140)
> at 
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:81)
> at 
> org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:650)
> at 
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:87)
> at 
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:342)
> at org.apache.coyote.ajp.AjpProcessor.service(AjpProcessor.java:479)
> at 
> org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
> at 
> org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:806)
> at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1498)
> at 
> org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at 
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
> at java.lang.Thread.run(Thread.java:748)
> 2019-05-14 13:50:53,598 INFO  
> org.dspace.app.webui.servlet.ShibbolethServlet @ 
> anonymous:session_id=A06D060FB96B3130E1635528953A1D1C:ip_addr=xxx.xxx.xxx.xxx:failed_login:result=4
>
> I'm not sure what I can do next to get this working. Can anyone help ?
>
> Thanks
>
> Jeff
>
>

-- 
All messages to this mailing list should adhere

[dspace-tech] 6.3 Feedback Form Spam

2019-05-15 Thread Library Systems 
We are running DSpace 6.3 and have been getting a daily spam message 
through the feedback form.  It is the same message, but it has different 
email addresses.  Is there a way to restrict the feedback form so that only 
logged-in users can leave feedback?  Or is there another way to control 
spam through this form?

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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/bee60425-265c-4850-a64f-9eba214b4df9%40googlegroups.com.

Re: [dspace-tech] How to compile only solr and jspui in DSpace 6.3

2019-05-15 Thread Claudia Jürgen 

Hi,

you can tell maven which profile(s) to build with
mvn package -pl package-name1,package-name2
but you have to keep the dependencies in mind

Hope this helps

Claudia Jürgen




Am 14.05.2019 um 19:21 schrieb Vinicius Assef:

Hi there.

I'm working in some tests with DSpace 6.3 in a local VM and I'd like to
compile only solr and jspui.

How could I get that?

Thanks in advance.

--
Vinicius Assef




--
Claudia Juergen
Eldorado

Technische Universität Dortmund
Universitätsbibliothek
Vogelpothsweg 76
44227 Dortmund

Tel.: +49 231-755 40 43
Fax: +49 231-755 40 32
claudia.juer...@tu-dortmund.de
www.ub.tu-dortmund.de

Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. Sie ist 
ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der für diese 
E-Mail bestimmte Adressat sein, unterrichten Sie bitte den Absender und 
vernichten Sie diese Mail. Vielen Dank.
Unbeschadet der Korrespondenz per E-Mail, sind unsere Erklärungen 
ausschließlich final rechtsverbindlich, wenn sie in herkömmlicher Schriftform 
(mit eigenhändiger Unterschrift) oder durch Übermittlung eines solchen 
Schriftstücks per Telefax erfolgen.

Important note: The information included in this e-mail is confidential. It is 
solely intended for the recipient. If you are not the intended recipient of 
this e-mail please contact the sender and delete this message. Thank you. 
Without prejudice of e-mail correspondence, our statements are only legally 
binding when they are made in the conventional written form (with personal 
signature) or when such documents are sent by fax.

--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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/5ca162f5-3997-5135-bd92-e9d7eae64558%40tu-dortmund.de.