[dspace-tech] Re: Ant fresh install error dspace-cris
Problems with permissions. -- 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 post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
[dspace-tech] Ant fresh install error dspace-cris
Hi, when I go to run ant fresh_install i have this error, and i cant fixit, thanks for your support! dspace@testing:/home/usercris/crisinstallation/DSpace/dspace/target/dspace-insta ller$ ant fresh_install Buildfile: /home/usercris/crisinstallation/DSpace/dspace/target/dspace-installer /build.xml init_installation: init_configs: BUILD FAILED /home/usercris/crisinstallation/DSpace/dspace/target/dspace-installer/build.xml: 796: java.io.IOException: can't write to read-only destination file /dspace/conf ig/ant.properties at org.apache.tools.ant.util.ResourceUtils.copyResource(ResourceUtils.ja va:409) at org.apache.tools.ant.taskdefs.Echo.execute(Echo.java:66) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.jav a:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:435) at org.apache.tools.ant.Target.performTasks(Target.java:456) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1393) at org.apache.tools.ant.Project.executeTarget(Project.java:1364) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExe cutor.java:41) at org.apache.tools.ant.Project.executeTargets(Project.java:1248) at org.apache.tools.ant.Main.runBuild(Main.java:851) at org.apache.tools.ant.Main.startAnt(Main.java:235) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109) -- 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 post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
[dspace-tech] modify images and styles in jspui
Good afternoon I need your help I just installed dspace 6.1 and everything was installed correctly the problem esque I can not modify the images in this case the logo of dspace the page tells me that it is in jspui / image but when I modify the image and go to the page and update it is still the same even delete all the images with the name of the image in my pc and still do not modify the interface I do not know where the image takes the page if you delete all the image folder inside C: \ tomcat \ webapps \ jspui \ image I also try to modify the C: \ tomcat \ webapps \ jspui \ static \ css \ bootstrap styles and it is not modified I delete the folder but the same does not modify anything I do not know what I'm doing wrong. -- 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 post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
Re: [dspace-tech] XMLUI: Submission verify step ignores type binding [repost]
Hi Marie-Hélène, Yes, I'd recommend a new JIRA ticket specific to the XMLUI, as the other JSPUI-specific ticket was already closed out. We can then link the two tickets up as related, so others can find both easily. Thanks! Tim On Wed, Oct 4, 2017 at 11:02 AM wrote: > Hi Tim, > Yes, will do (i.e. contribute back). Meanwhile should I fill a new JIRA > ticket for this specific issue with XMLUI? > > Marie-Hélène Vézina > > > On Wednesday, 4 October 2017 10:38:07 UTC-4, Tim Donohue wrote: > >> Hi Marie-Hélène, >> >> It looks like this issue was only fixed specifically in the JSPUI. If >> you've found the same issue in the XMLUI, we'd welcome contributing any >> code back (via a GitHub Pull Request or similar). See also our Code >> Contribution Guidelines: >> https://wiki.duraspace.org/display/DSPACE/Code+Contribution+Guidelines >> >> I've also added a comment to this effect to that DS-3229 ticket. >> >> Tim >> >> On Wed, Oct 4, 2017 at 8:26 AM wrote: >> > Just before to embark in homemade code developping I'm reposting in case >>> someone somewhere already did this work and would be willing to share >>> >>> >>> On Wednesday, 30 August 2017 16:24:53 UTC-4, mh.vezi...@gmail.com wrote: >>> Hi All, >>> >>> I am running Dspace 5.5 XMLUI Mirage. >>> >>> I do have the exact same problem with the xmlui interface as the one >>> described here: https://jira.duraspace.org/browse/DS-3229 >>> >>> Is there an equivalent in XMLUI for the patch made for JSPUI? >>> >>> Thanks to let me know. >>> >>> Marie-Hélène Vézina >>> Bibliothèques, Université de Montréal >>> >>> -- >>> 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...@googlegroups.com. >>> To post to this group, send email to dspac...@googlegroups.com. >> >> >>> Visit this group at https://groups.google.com/group/dspace-tech. >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- >> >> Tim Donohue >> Technical Lead for DSpace & DSpaceDirect >> DuraSpace.org | DSpace.org | DSpaceDirect.org >> >> -- > 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 post to this group, send email to dspace-tech@googlegroups.com. > Visit this group at https://groups.google.com/group/dspace-tech. > For more options, visit https://groups.google.com/d/optout. > -- Tim Donohue Technical Lead for DSpace & DSpaceDirect DuraSpace.org | DSpace.org | DSpaceDirect.org -- 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 post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
Re: [dspace-tech] XMLUI: Submission verify step ignores type binding [repost]
Hi Tim, Yes, will do (i.e. contribute back). Meanwhile should I fill a new JIRA ticket for this specific issue with XMLUI? Marie-Hélène Vézina On Wednesday, 4 October 2017 10:38:07 UTC-4, Tim Donohue wrote: > > Hi Marie-Hélène, > > It looks like this issue was only fixed specifically in the JSPUI. If > you've found the same issue in the XMLUI, we'd welcome contributing any > code back (via a GitHub Pull Request or similar). See also our Code > Contribution Guidelines: > https://wiki.duraspace.org/display/DSPACE/Code+Contribution+Guidelines > > I've also added a comment to this effect to that DS-3229 ticket. > > Tim > > On Wed, Oct 4, 2017 at 8:26 AM > wrote: > >> Just before to embark in homemade code developping I'm reposting in case >> someone somewhere already did this work and would be willing to share >> >> >> On Wednesday, 30 August 2017 16:24:53 UTC-4, mh.vezi...@gmail.com wrote: >> Hi All, >> >> I am running Dspace 5.5 XMLUI Mirage. >> >> I do have the exact same problem with the xmlui interface as the one >> described here: https://jira.duraspace.org/browse/DS-3229 >> >> Is there an equivalent in XMLUI for the patch made for JSPUI? >> >> Thanks to let me know. >> >> Marie-Hélène Vézina >> Bibliothèques, Université de Montréal >> >> -- >> 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...@googlegroups.com . >> To post to this group, send email to dspac...@googlegroups.com >> . >> Visit this group at https://groups.google.com/group/dspace-tech. >> For more options, visit https://groups.google.com/d/optout. >> > -- > > Tim Donohue > Technical Lead for DSpace & DSpaceDirect > DuraSpace.org | DSpace.org | DSpaceDirect.org > > -- 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 post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
RE: [dspace-tech] RE: submissions time out but still work
Hi Tim, Thanks for the info. FYI, we are running DSpace 5.8 on Ubuntu 14.04 LTS and PostgreSQL. We run Apache and Tomcat7. I tried to view the logs while my colleague did a deposit through the UI. The /dspace/log/solr.log file didn’t show any errors. However, I did notice some errors/warnings in our /dspace/log/cocoon.log.2017-10-04 during the time frame of the deposit. 2017-10-04 10:39:32,176 WARN cocoon.access - org.apache.cocoon.ConnectionResetException: Connection reset by peer at - jndi:/localhost/sitemap.xmap:256:68 at - jndi:/localhost/sitemap.xmap:255:88 at - jndi:/localhost/sitemap.xmap:254:70 2017-10-04 10:39:38,951 ERROR cocoon.handled - Could not read resource cocoon://DRI/1/handle/10012/9972/workflow at - jndi:/localhost/aspects/aspects.xmap:85:34 at - jndi:/localhost/aspects/aspects.xmap:84:43 at - jndi:/localhost/aspects/aspects.xmap:83:22 at - jndi:/localhost/themes/Mirage2/sitemap.xmap:198:56 at - jndi:/localhost/themes/Mirage2/sitemap.xmap:108:54 at - jndi:/localhost/themes/Mirage2/sitemap.xmap:102:44 at - jndi:/localhost/themes/Mirage2/sitemap.xmap:98:49 at - jndi:/localhost/themes/Mirage2/sitemap.xmap:85:51 at - jndi:/localhost/themes/Mirage2/sitemap.xmap:82:54 at - jndi:/localhost/themes/Mirage2/sitemap.xmap:190:67 at - jndi:/localhost/themes/Mirage2/sitemap.xmap:185:37 org.apache.cocoon.ProcessingException: Could not read resource cocoon://DRI/1/handle/10012/9972/workflow at - jndi:/localhost/aspects/aspects.xmap:85:34 at - jndi:/localhost/aspects/aspects.xmap:84:43 at - jndi:/localhost/aspects/aspects.xmap:83:22 at - jndi:/localhost/themes/Mirage2/sitemap.xmap:198:56 at - jndi:/localhost/themes/Mirage2/sitemap.xmap:108:54 at - jndi:/localhost/themes/Mirage2/sitemap.xmap:102:44 at - jndi:/localhost/themes/Mirage2/sitemap.xmap:98:49 at - jndi:/localhost/themes/Mirage2/sitemap.xmap:85:51 at - jndi:/localhost/themes/Mirage2/sitemap.xmap:82:54 at - jndi:/localhost/themes/Mirage2/sitemap.xmap:190:67 at - jndi:/localhost/themes/Mirage2/sitemap.xmap:185:37 at org.apache.cocoon.components.source.util.SourceUtil.handleSAXException(SourceUtil.java:409) at org.apache.cocoon.generation.FileGenerator.generate(FileGenerator.java:138) at sun.reflect.GeneratedMethodAccessor150.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71) at com.sun.proxy.$Proxy92.generate(Unknown Source) at org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.processXMLPipeline(AbstractProcessingPipeline.java:544) at org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipeline.processXMLPipeline(AbstractCachingProcessingPipeline.java:273) at org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.process(AbstractProcessingPipeline.java:750) at sun.reflect.GeneratedMethodAccessor151.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71) at com.sun.proxy.$Proxy91.process(Unknown Source) at org.apache.cocoon.components.source.impl.SitemapSource.toSAX(SitemapSource.java:362) at org.apache.cocoon.components.source.util.SourceUtil.toSAX(SourceUtil.java:111) at org.apache.cocoon.components.source.util.SourceUtil.parse(SourceUtil.java:294) at org.apache.cocoon.generation.FileGenerator.generate(FileGenerator.java:136) at sun.reflect.GeneratedMethodAccessor150.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71) at com.sun.proxy.$Proxy92.generate(Unknown Source) at org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.processXMLPipeline(AbstractProcessingPipeline.java:544) at org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipeline.processXMLPipeline(AbstractCachingProcessingPipeline.java:273) at org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.process(AbstractProcessingPipeline.java:439) at sun.reflect.GeneratedMethodAccessor85.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.M
Re: [dspace-tech] Image processing in python run in dspace
Hello Nitharshini, I think you may be on the wrong mailing list. It sounds like you might be asking about something from https://www.dspace.com/. This mailing list is for an entirely different DSpace organization/product ( dspace.org), and we don't have anything called a "microautobox2". - Tim On Tue, Oct 3, 2017 at 10:39 PM Nitharshini Sivakumar < nitharshinis...@gmail.com> wrote: > Hi! > > I have a microautobox2. I wanted to run a few python codes related to imge > processing on it. Anybody can help me out in and let me know how to do this? > > -- > 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 post to this group, send email to dspace-tech@googlegroups.com. > Visit this group at https://groups.google.com/group/dspace-tech. > For more options, visit https://groups.google.com/d/optout. > -- Tim Donohue Technical Lead for DSpace & DSpaceDirect DuraSpace.org | DSpace.org | DSpaceDirect.org -- 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 post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
Re: [dspace-tech] XMLUI: Submission verify step ignores type binding [repost]
Hi Marie-Hélène, It looks like this issue was only fixed specifically in the JSPUI. If you've found the same issue in the XMLUI, we'd welcome contributing any code back (via a GitHub Pull Request or similar). See also our Code Contribution Guidelines: https://wiki.duraspace.org/display/DSPACE/Code+Contribution+Guidelines I've also added a comment to this effect to that DS-3229 ticket. Tim On Wed, Oct 4, 2017 at 8:26 AM wrote: > Just before to embark in homemade code developping I'm reposting in case > someone somewhere already did this work and would be willing to share > > > On Wednesday, 30 August 2017 16:24:53 UTC-4, mh.vezi...@gmail.com wrote: > Hi All, > > I am running Dspace 5.5 XMLUI Mirage. > > I do have the exact same problem with the xmlui interface as the one > described here: https://jira.duraspace.org/browse/DS-3229 > > Is there an equivalent in XMLUI for the patch made for JSPUI? > > Thanks to let me know. > > Marie-Hélène Vézina > Bibliothèques, Université de Montréal > > -- > 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 post to this group, send email to dspace-tech@googlegroups.com. > Visit this group at https://groups.google.com/group/dspace-tech. > For more options, visit https://groups.google.com/d/optout. > -- Tim Donohue Technical Lead for DSpace & DSpaceDirect DuraSpace.org | DSpace.org | DSpaceDirect.org -- 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 post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
Re: [dspace-tech] ip authentication, how do I log in?
Hi Paul, Yes, it should "just work". As Claudia also noted, it'd be useful to know what version of DSpace you are running (as I vaguely recall a few versions had bugs in the IP auth at times). Regarding the user's group, if you are expecting the user to appear as a member of the Group in the Admin UI (via the Group Edit tools), that actually will not happen. When using IP Auth, the user is only a temporary Group member based on their current session (i.e. they are only a member within their specific session and after their session ends, the user is no longer a member of that group) So, as Claudia notes/implies, the ways to tell this is working are: * Check if the permissions given to the group are applied when you access the site from the given IP address (sounds like you tried this though) * Or, actually login/authenticate (from the IP address) and check the user's profile (My DSpace) page to see if the Group is listed there. This is only visible for logged in users though, and won't be visible to anonymous users. - Tim On Wed, Oct 4, 2017 at 2:33 AM Paul Warner wrote: > Dear Tim, > > Thanks for your reply. What you describe is exactly what we need. I can > see my use of the phrase 'logging in' was misleading. I have everything > set up to verify ip authentication/authorization, as far as I know. But > when I come to my dspace in the browser, and it is clear from the log that > dspace knows the ip address, and it matches what is in > authentication-ip.cfg, it still does not put the user in the desired group > or give the user permission to listen to the audio files. It sounds, from > your email, that this is supposed to just work, one does not need to do > anything more than come to the site from the designated ip address, in > order to have access to the files. > > Originally I thought that perhaps the authentication module was not > getting the right ip address, since I am using apache in front of tomcat, > but then I found that the module has this built in, when you uncomment > useProxies = true in the dspace.cfg. And having done that, I can see the > ip in the dspace log file. But the user still does not land in the right > group... > > Best regards, > Paul > > > On Tue, Oct 3, 2017 at 4:21 PM, Tim Donohue > wrote: > >> Hi Paul, >> >> IP Authentication is a slight misnomer. It's not truly *authentication* >> but rather *authorization*. So, you don't need to login at all, but you >> are provided specific access rights based on your IP address. >> >> So, the point of IP Auth is that you are essentially "mapping" specific >> IP addresses or ranges to specific DSpace Groups. Anyone who accesses your >> site from those IP addresses (even anonymously) will be added to that >> DSpace Group for the remainder of their session. You can then use that >> DSpace Group to assign those users specific access rights. >> >> One example use case for IP Auth is to provide access to all University >> Theses & Dissertations while on campus (or while in the University >> Library). In such a scenario, the Theses & Dissertations may be access >> restricted to downloading/viewing to the general public, but if a user >> visits your site from an on-campus IP address, they can download/view the >> files without logging in. >> >> I hope that helps clarify the purpose of IP Auth! >> >> Tim >> >> On Mon, Oct 2, 2017 at 5:11 AM Paul Warner wrote: >> >>> Hi, >>> >>> I have set up ip authentication using apache as a proxy front end for >>> tomcat. The log is seeing the ip address, so it is being correctly passed >>> through from apache to tomcat, and correctly read by dspace. But it is not >>> logging me in to the group. My question is, how do I log in? If I have ip >>> authentication stacked with password authentication, when I click the login >>> button in the top menu on the jspui, I go to the password login page. If I >>> remove password login from the list in authentication.cfg and have only ip >>> authentication, then when I click the login button I get a page with no >>> form elements at all, nothing. And, as I said, I am not being logged in to >>> the group automatically. >>> >>> Thanks for any hints or tips! >>> >>> Best regards, >>> Paul >>> >>> dspace 6.1 on Suse 12.2, tomcat 8 and apache 2.4.23 >>> >>> Here is the log entry: >>> >>> 2017-10-02 11:55:00,242 INFO org.dspace.usage.LoggerUsageEventListener >>> @ anonymous:session_id=50601B9E86D5FEC0FC1173927BAF8DA6:ip_addr=1.2.3.4: >>> view_item:handle=123456789/46 >>> >>> I have configured dspace so: >>> >>> from dspace.cfg >>> >>> Proxy Settings >>> ## >>> >>> # uncomment and specify both properties if proxy server >>> required >>> >>> # proxy server for external http requests - use regular hostname without >>> port >>> number >>> >>> http.proxy.host = localhost >>> >>> # port number of proxy >>> server >>> >>> http.proxy.port = 443 >>> >>> # If enabled, the logging and the Solr statistics system will look >>> for >>> >>> # an X-Forwarded-
Re: [dspace-tech] Re: Export collection into CSV need add Has file field
Hello, the information (whether an item has a file in the bundle original) is available in the solr search index see http://demo.dspace.org/xmlui/handle/10673/1/discover?filtertype=has_content_in_original_bundle&filter_relational_operator=equals&filter=true Hope this helps Claudia Jürgen Am 27.09.2017 um 11:10 schrieb Bhavesh Patel: Thank you Bob for your mail. Is there any way to take report from directly from database (executing select query) for particular collection? Regards, Bhavesh Thanks & Regards, *Bhavesh R. Patel* *"Learning is a never ending process"* On Tue, Sep 26, 2017 at 5:20 AM, Bob Dougherty wrote: Bhavesh, There is no metadata field indicating whether an item has any uploaded files. So you can't expect to get that information in the metadata export. You can use the API to get information about files (bitstreams), but that is not nearly as easy as downloading a CSV file. -Bob On Monday, September 25, 2017 at 7:03:57 AM UTC-4, Bhavesh Patel wrote: Dear All, This email regarding to the Export Metadata facility feature from User Interface - Administrator panel in XMLUI. [image: Inline image 1] Once we export into CSV it will not showing the Has file (If file is uploaded) field, Is there any way to add this field into the CSV file? DSpace: 6.0 Interface: XMLUI OS: CentOS 7 - 64-bit Thanks & Regards, *Bhavesh R. Patel* *"Learning is a never ending process"* -- 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 post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout. -- 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. -- 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 post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
Re: [dspace-tech] ip authentication, how do I log in?
Hello Paul, btw. with which version an UI are you working? We are using IP based authentication for campus restriced material and it works fine (5.x, jspui). Having stacked IP Authentication in dspace/config/modules/authentication.cfg like plugin.sequence.org.dspace.authenticate.AuthenticationMethod = \ org.dspace.authenticate.PasswordAuthentication, \ org.dspace.authenticate.IPAuthentication and adding matching the ip to the group in dspace/config/modules/authentication-ip.cfg like ip.Campus\ Group = [some ip pattern] works fine, assuming the resources got the right resource policies. (Note, if you got a blank in your group name you got to escape it with \) One easy test to see, whether a user is added to this group is setting dspace/config/dspace.cfg webui.mydspace.showgroupmemberships = true (defaults to false) This will show list of all the groups on the my dspace page of a user. If the user is added to the group and still can not access a resource, check the resource policies. Hope this helps Claudia Jürgen Am 04.10.2017 um 09:33 schrieb Paul Warner: Dear Tim, Thanks for your reply. What you describe is exactly what we need. I can see my use of the phrase 'logging in' was misleading. I have everything set up to verify ip authentication/authorization, as far as I know. But when I come to my dspace in the browser, and it is clear from the log that dspace knows the ip address, and it matches what is in authentication-ip.cfg, it still does not put the user in the desired group or give the user permission to listen to the audio files. It sounds, from your email, that this is supposed to just work, one does not need to do anything more than come to the site from the designated ip address, in order to have access to the files. Originally I thought that perhaps the authentication module was not getting the right ip address, since I am using apache in front of tomcat, but then I found that the module has this built in, when you uncomment useProxies = true in the dspace.cfg. And having done that, I can see the ip in the dspace log file. But the user still does not land in the right group... Best regards, Paul On Tue, Oct 3, 2017 at 4:21 PM, Tim Donohue wrote: Hi Paul, IP Authentication is a slight misnomer. It's not truly *authentication* but rather *authorization*. So, you don't need to login at all, but you are provided specific access rights based on your IP address. So, the point of IP Auth is that you are essentially "mapping" specific IP addresses or ranges to specific DSpace Groups. Anyone who accesses your site from those IP addresses (even anonymously) will be added to that DSpace Group for the remainder of their session. You can then use that DSpace Group to assign those users specific access rights. One example use case for IP Auth is to provide access to all University Theses & Dissertations while on campus (or while in the University Library). In such a scenario, the Theses & Dissertations may be access restricted to downloading/viewing to the general public, but if a user visits your site from an on-campus IP address, they can download/view the files without logging in. I hope that helps clarify the purpose of IP Auth! Tim On Mon, Oct 2, 2017 at 5:11 AM Paul Warner wrote: Hi, I have set up ip authentication using apache as a proxy front end for tomcat. The log is seeing the ip address, so it is being correctly passed through from apache to tomcat, and correctly read by dspace. But it is not logging me in to the group. My question is, how do I log in? If I have ip authentication stacked with password authentication, when I click the login button in the top menu on the jspui, I go to the password login page. If I remove password login from the list in authentication.cfg and have only ip authentication, then when I click the login button I get a page with no form elements at all, nothing. And, as I said, I am not being logged in to the group automatically. Thanks for any hints or tips! Best regards, Paul dspace 6.1 on Suse 12.2, tomcat 8 and apache 2.4.23 Here is the log entry: 2017-10-02 11:55:00,242 INFO org.dspace.usage.LoggerUsageEventListener @ anonymous:session_id=50601B9E86D5FEC0FC1173927BAF8DA6:ip_addr=1.2.3.4: view_item:handle=123456789/46 I have configured dspace so: from dspace.cfg Proxy Settings ## # uncomment and specify both properties if proxy server required # proxy server for external http requests - use regular hostname without port number http.proxy.host = localhost # port number of proxy server http.proxy.port = 443 # If enabled, the logging and the Solr statistics system will look for # an X-Forwarded-For header. If it finds it, it will use this for the user IP address useProxies = true from authentication.cfg plugin.sequence.org.dspace.authenticate.AuthenticationMethod = org.dspace.authenticate.IPAuthentication,org.dspace.authenticate. PasswordAuthentication from authentication-ip.cfg
[dspace-tech] XMLUI: Submission verify step ignores type binding [repost]
Just before to embark in homemade code developping I'm reposting in case someone somewhere already did this work and would be willing to share On Wednesday, 30 August 2017 16:24:53 UTC-4, mh.vezi...@gmail.com wrote: Hi All, I am running Dspace 5.5 XMLUI Mirage. I do have the exact same problem with the xmlui interface as the one described here: https://jira.duraspace.org/browse/DS-3229 Is there an equivalent in XMLUI for the patch made for JSPUI? Thanks to let me know. Marie-Hélène Vézina Bibliothèques, Université de Montréal -- 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 post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
Re: [dspace-tech] ip authentication, how do I log in?
Dear Tim, Thanks for your reply. What you describe is exactly what we need. I can see my use of the phrase 'logging in' was misleading. I have everything set up to verify ip authentication/authorization, as far as I know. But when I come to my dspace in the browser, and it is clear from the log that dspace knows the ip address, and it matches what is in authentication-ip.cfg, it still does not put the user in the desired group or give the user permission to listen to the audio files. It sounds, from your email, that this is supposed to just work, one does not need to do anything more than come to the site from the designated ip address, in order to have access to the files. Originally I thought that perhaps the authentication module was not getting the right ip address, since I am using apache in front of tomcat, but then I found that the module has this built in, when you uncomment useProxies = true in the dspace.cfg. And having done that, I can see the ip in the dspace log file. But the user still does not land in the right group... Best regards, Paul On Tue, Oct 3, 2017 at 4:21 PM, Tim Donohue wrote: > Hi Paul, > > IP Authentication is a slight misnomer. It's not truly *authentication* > but rather *authorization*. So, you don't need to login at all, but you > are provided specific access rights based on your IP address. > > So, the point of IP Auth is that you are essentially "mapping" specific IP > addresses or ranges to specific DSpace Groups. Anyone who accesses your > site from those IP addresses (even anonymously) will be added to that > DSpace Group for the remainder of their session. You can then use that > DSpace Group to assign those users specific access rights. > > One example use case for IP Auth is to provide access to all University > Theses & Dissertations while on campus (or while in the University > Library). In such a scenario, the Theses & Dissertations may be access > restricted to downloading/viewing to the general public, but if a user > visits your site from an on-campus IP address, they can download/view the > files without logging in. > > I hope that helps clarify the purpose of IP Auth! > > Tim > > On Mon, Oct 2, 2017 at 5:11 AM Paul Warner wrote: > >> Hi, >> >> I have set up ip authentication using apache as a proxy front end for >> tomcat. The log is seeing the ip address, so it is being correctly passed >> through from apache to tomcat, and correctly read by dspace. But it is not >> logging me in to the group. My question is, how do I log in? If I have ip >> authentication stacked with password authentication, when I click the login >> button in the top menu on the jspui, I go to the password login page. If I >> remove password login from the list in authentication.cfg and have only ip >> authentication, then when I click the login button I get a page with no >> form elements at all, nothing. And, as I said, I am not being logged in to >> the group automatically. >> >> Thanks for any hints or tips! >> >> Best regards, >> Paul >> >> dspace 6.1 on Suse 12.2, tomcat 8 and apache 2.4.23 >> >> Here is the log entry: >> >> 2017-10-02 11:55:00,242 INFO org.dspace.usage.LoggerUsageEventListener >> @ anonymous:session_id=50601B9E86D5FEC0FC1173927BAF8DA6:ip_addr=1.2.3.4: >> view_item:handle=123456789/46 >> >> I have configured dspace so: >> >> from dspace.cfg >> >> Proxy Settings ## >> >> >> # uncomment and specify both properties if proxy server >> required >> >> # proxy server for external http requests - use regular hostname without >> port number >> >> http.proxy.host = localhost >> >> # port number of proxy server >> >> >> http.proxy.port = 443 >> >> # If enabled, the logging and the Solr statistics system will look >> for >> >> # an X-Forwarded-For header. If it finds it, it will use this for the >> user IP address >> >> useProxies = true >> >> from authentication.cfg >> >> plugin.sequence.org.dspace.authenticate.AuthenticationMethod = >> org.dspace.authenticate.IPAuthentication,org.dspace.authenticate. >> PasswordAuthentication >> >> from authentication-ip.cfg >> >> authentication-ip.Hochschule_Bibliothek = 1.2.3.4 >> >> -- >> 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 post to this group, send email to dspace-tech@googlegroups.com. >> Visit this group at https://groups.google.com/group/dspace-tech. >> For more options, visit https://groups.google.com/d/optout. >> > -- > > Tim Donohue > Technical Lead for DSpace & DSpaceDirect > DuraSpace.org | DSpace.org | DSpaceDirect.org > > -- 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 post to this group, send e
