[dspace-tech] OAuth for email servers

[Mong Khon]

Hi all,

Microsoft has strongly advised not to use SMTP Auth as it will not be 
supported in the future
,leaving OAuth as the only viable authentication type 
(https://learn.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/deprecation-of-basic-authentication-exchange-online)

We are trying to figure out whether SMTP authentication using OAuth is 
supported on DSpace. If so, how can we configure this?

Kind regards,
Mong

-- 
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/843a5366-3cee-401e-b45a-4b5e437d65b3n%40googlegroups.com.

[dspace-tech] odd/faulty search behavior

[Paige Morgan]

This is something that I'm seeing in my local repository, but can also
reproduce in the demo site. I figured I'd check before submitting a bug
report.

If you search for a term (like "schools"), you get some results:
https://demo7.dspace.org/search?query=schools

Let's say you go to the 7th page of the results:
https://demo7.dspace.org/search?query=schools=7

>From that page, if you type a new term into the search bar ("All of
DSpace") or the magnifying glass search at the upper right, DSpace will
repeat the search -- but will hang on to whatever page you were at:

[image: image.png]

For example: if you search for "kittens", it will search to see whether
DSpace has a page 7 for "kitten" results, and it will tell you that there
are no results.

https://demo7.dspace.org/search?query=kittens=7

But -- if you go back to the homepage, and then search for "kittens", then
you *do* get results: https://demo7.dspace.org/search?query=kittens

Is this a known bug? I don't see it on the Github site, but figured I'd
check before I submitted a ticket.

Thanks,
Paige


-
*Meeting/regular work hours: Monday - Thursday, 9am-5pm; limited email on
Friday mornings.*

Dr. Paige C. Morgan
(she/her/they)
Digital Publishing and Copyright Librarian,
Head of Digital Initiatives & Preservation
University of Delaware Library, Museums and Press (on Lenape land
)
Morris 118
ORCID: https://orcid.org/-0001-8076-7356
paig...@udel.edu
302.831.7153

Make an appointment to meet with me: https://calendly.com/paigecm/ (Meetings
available via Zoom, phone, etc.)
*** I observe email-free evenings and weekends. ***

-- 
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/CA%2BzEVd%3D8BxMho9-xo%3DRfHZ9RT7gLXKADHnLrTC7OTdAJRjQgLA%40mail.gmail.com.

Re: [dspace-tech] Re: Error with searching authorizations

[Duy Minh]

Hi,

Thanks for the help. It turns out I *did* forget to add the  
X-Forwarded-Proto header to the proxy after all.

In case anyone encounters the same problem, for Apache 2, add the line 
"RequestHeader set X-Forwarded-Proto https" to default-000-le-ssl.conf.

Thanks again for your assistance.

Regards,
Minh

On Thursday, 1 December 2022 at 03:28:41 UTC+7 Tim Donohue wrote:

> Hi Minh,
>
> According to the initial error you shared (in your dspace.log), it's 
> showing that something is trying to contact your backend using "
> http://vinspace.online/server/;.  NOTICE that it is trying to access 
> "http" instead of "https"!
>
> Your configs you shared look correct to me... and they both specify 
> HTTPS.  So, it's unclear to me why your UI would be sending an HTTP request 
> to the backend instead of HTTPS.
>
> Maybe you updated the wrong "config.*.yml" on the frontend?  Or maybe 
> something is being cached on either the frontend or backend?  It also could 
> be that whatever proxy you may be using could require the 
> "X-Forwarded-Proto" header.  See this common installation issue: 
> https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-MyRESTAPIisrunningunderHTTPS,butsomeofits%22link%22URLsareswitchingtoHTTP?
>
> Tim
> --
> *From:* dspac...@googlegroups.com  on behalf 
> of Duy Minh 
> *Sent:* Tuesday, November 29, 2022 8:23 PM
> *To:* DSpace Technical Support 
> *Subject:* [dspace-tech] Re: Error with searching authorizations 
>  
> Hi Tim, 
>
> Both the backend and frontend sides seem to be correct. Please find the 
> relevant settings below:
> [image: Screenshot 2022-11-30 084609.png][image: Screenshot 2022-11-30 
> 085327.png]
>
> Is there anything I overlooked? Or could the problem be somewhere else?
>
> Regards,
> Minh
> On Wednesday, 30 November 2022 at 04:41:38 UTC+7 Tim Donohue wrote:
>
> Hi Minh,
>
> That "the supplied uri is not ours" error appears to be saying that the 
> URI sent to your REST API doesn't match what is set in your 
> "dspace.server.url" setting (on the backend's local.cfg).  So you may want 
> to verify that "dspace.server.url" setting is correct... the error you 
> shared seems to think it *should be* something like 
> http://vinspace.online/server/.  Either that, or maybe your UI's 
> configuration has the wrong URL in its "rest" settings and is trying to 
> access your REST API via a different URL. 
>
> Tim
>
> On Monday, November 28, 2022 at 6:16:14 AM UTC-6 duymin...@gmail.com 
> wrote:
>
> Hi all, 
>
> After deploying the DSpace 7.4 frontend and backend, the frontend 
> (accessible at https://vinspace.online/home) seems to be missing features 
> such as registration. Looking at the dev console shows a series of 400 
> error codes corresponding to the API requests for searching authorizations 
> of features.  
>
> The tomcat error logs show HTTP request parsing errors :
> [image: 2022-11-28.png]
> And the dspace logs show multiple warnings stating "the supplied uri is 
> not ours":
> [image: 2022-11-28 (2).png]
>
> Please advise.
>
> Regards,
> Minh
>
> -- 
> 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 a topic in the 
> Google Groups "DSpace Technical Support" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/dspace-tech/Y0bcDpSzIxc/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> dspace-tech...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/dspace-tech/28706f71-0d14-4b06-a2f5-7134065384ffn%40googlegroups.com
>  
> 
> .
>

-- 
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/d4d2f6a6-eedf-4a8e-9cac-cdca4f9f0187n%40googlegroups.com.

[dspace-tech] Turning on search snippets/hit highlighting generates snippets for some items, but not for others

[Paige Morgan]

We recently turned on the search snippets/hit highlighting
 function for our IR
(currently running DSpace 7.4).

It works, but only on certain documents. You can see an example of this by
searching our repository for "parties":
https://udspace.udel.edu/search?query=parties=2

All of the items in the search results have been OCR'd, so if you download
the item and search for the term, it's findable -- but I'm not clear on why
snippets would show on some items, but not on others.  From what I can see,
this isn't format-based -- some PDFs show snippets, while others don't --
though it looks as though documents from our digital collections (digitized
newspapers and other documents) are much less likely to have snippets
available. Similarly, PDFs that were generated from slidedecks also aren't
showing snippets, and phrases from these sorts of documents don't return
any hits when searched for in our repository.

I'm concerned -- does this indicate that our indexing might not be
functioning effectively/completely, or that we might have turned on a
setting to selectively index some collections, and not others?

Any advice/recommendations appreciated.

Paige


-
*Meeting/regular work hours: Monday - Thursday, 9am-5pm; limited email on
Friday mornings.*

Dr. Paige C. Morgan
(she/her/they)
Digital Publishing and Copyright Librarian,
Head of Digital Initiatives & Preservation
University of Delaware Library, Museums and Press (on Lenape land
)
Morris 118
ORCID: https://orcid.org/-0001-8076-7356
paig...@udel.edu
302.831.7153

Make an appointment to meet with me: https://calendly.com/paigecm/ (Meetings
available via Zoom, phone, etc.)
*** I observe email-free evenings and weekends. ***

-- 
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/CA%2BzEVdnrWAimA8h5-96uz5NqvMD5m4g3Mnp02jzydyWk67HfGw%40mail.gmail.com.