[dspace-tech] 401 unauthorized error during ORCID login DSpace ver 7.4
Hi All, I have enabled ORCID login using sandbox, when login the following screenshot appears: [image: 401 unauthorized.png] login details have been registered on DSpace as normal administrator. how to share OTCID account email address with DSpace. Please advise or refer me to pages that may help. Note attached bottom part of dspace.log Regards, Lewatle -- 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/c8cdd12f-4831-453b-b64f-2a75bc4dcfc3n%40googlegroups.com. $ tail -n 30 dspace.log 2022-12-05 09:33:03,356 INFO 54ead904-4c0b-4636-8d96-89b6f466f76e 5052ec19-c910-4b5d-b213-e17059635705 org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request [GET /server/api/authz/authorizations/search/object] originated from /handle/20.500.12430/420382/discover?field=subject=subject_relational_operator=equals=CODESA%2B1%2BDeclaration%2Bof%2Bintent 2022-12-05 09:33:03,356 INFO 54ead904-4c0b-4636-8d96-89b6f466f76e a14bcbc8-08f4-48cd-ab26-0654e56cba14 org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request [GET /server/api/authz/authorizations/search/object] originated from /handle/20.500.12430/420382/discover?field=subject=subject_relational_operator=equals=CODESA%2B1%2BDeclaration%2Bof%2Bintent 2022-12-05 09:33:03,356 INFO 54ead904-4c0b-4636-8d96-89b6f466f76e 1d6e3f3b-a078-4db0-ab7e-997cf1d94328 org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request [GET /server/api/authz/authorizations/search/object] originated from /handle/20.500.12430/420382/discover?field=subject=subject_relational_operator=equals=CODESA%2B1%2BDeclaration%2Bof%2Bintent 2022-12-05 09:33:03,359 INFO 54ead904-4c0b-4636-8d96-89b6f466f76e 7a49b7c3-1ece-4900-9f7a-69da5e56d4c4 org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request [GET /server/api/authz/authorizations/search/object] originated from /handle/20.500.12430/420382/discover?field=subject=subject_relational_operator=equals=CODESA%2B1%2BDeclaration%2Bof%2Bintent 2022-12-05 09:33:03,360 INFO 54ead904-4c0b-4636-8d96-89b6f466f76e 07743366-e5c7-4b7b-8234-63b6faeebf2f org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request [GET /server/api/authz/authorizations/search/object] originated from /handle/20.500.12430/420382/discover?field=subject=subject_relational_operator=equals=CODESA%2B1%2BDeclaration%2Bof%2Bintent 2022-12-05 09:33:11,565 INFO unknown 30b972c4-5d6b-40e3-8a59-e8d3d86f532c org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request [GET /server/api] originated from / 2022-12-05 09:33:11,621 INFO abfe82b7-add4-400c-a593-ed41ec0867e8 f06571d5-25b0-4d9c-ad0c-56162388f326 org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request [GET /server/api/authn/status] originated from / 2022-12-05 09:33:11,646 INFO abfe82b7-add4-400c-a593-ed41ec0867e8 fdf9d2de-a4de-410d-957c-d664c1813348 org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request [GET /server/api] originated from / 2022-12-05 09:33:11,675 INFO abfe82b7-add4-400c-a593-ed41ec0867e8 7950fd7d-1f4b-459d-8d40-93cff9d0ac61 org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request [GET /server/api] originated from / 2022-12-05 09:33:11,785 INFO abfe82b7-add4-400c-a593-ed41ec0867e8 ed182a74-279f-4e5f-bd30-8795b6c22702 org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request [GET /server/api/core/sites] originated from / 2022-12-05 09:33:11,880 INFO abfe82b7-add4-400c-a593-ed41ec0867e8 99413a86-06a1-4d24-ad9f-b53e2c54a157 org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request [GET /server/api/authz/authorizations/search/object] originated from / 2022-12-05 09:33:12,730 INFO abfe82b7-add4-400c-a593-ed41ec0867e8 6d84c555-655b-4265-afcf-0b6705c8de0e org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request [GET /server/api/system/scripts/metadata-export] originated from / 2022-12-05 09:33:12,730 INFO abfe82b7-add4-400c-a593-ed41ec0867e8 44c948ab-5674-4c3d-ab50-06a7ae117755 org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request [GET /server/api/authz/authorizations/search/object] originated from / 2022-12-05 09:33:12,730 INFO abfe82b7-add4-400c-a593-ed41ec0867e8 723aff3e-394a-496d-bf5b-38a9302bd50b org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request [GET /server/api/authz/authorizations/search/object] originated from / 2022-12-05 09:33:12,732 INFO abfe82b7-add4-400c-a593-ed41ec0867e8 2ec66615-e325-46d8-827c-381053d96653
[dspace-tech] Re: How to disable klaro?
You got the 404 page not found error because you needed to run [dspace]/index-discovery after the change you have made to this item. Try the steps you see below. It should fix it. 1) /dspace/bin/dspace database migrate 2) /dspace/bin/dspace database validate 3) /dspace/bin/dspace database status 4) Change using pgAdmin https://hdl.handle.net/your-handle-prefix/1916 to https://your-server-domain-name/handle/your-handle-prefix/1916 5) /dspace/bin/dspace index-discovery -f -i e56a5422-b32b-4000-95dd-86467ef21c35 6) Copy over the old assetstore folder from the old server to the new Ubuntu server into /dspace/assetstore folder. 7) Try to access this item you changed and try download to PDF file. You are a stubborn man I must admin :-). Hop it helps you. On Saturday, November 26, 2022 at 2:47:04 AM UTC+3 Night Librarian wrote: > Thank you for the suggestion. I changed the dc.identifier.uri from > https://hdl.handle.net/your-handle-prefix/1916 by > https://my-server-domain-name/handle/my-handle-prefix/1916. Now, if I try > to open > https://my-server-domain-name/handle/my-handle-prefix/1916 in the > browser, I get 404 page not found. If I search for the item's title in all > of DSpace, and then try to download the pdf from there, I still can see the > pdf in the browser, but downloading it still doesn't work. > > In terms of Handle server, I wonder whether copy/pasting > [dspace]/handle-server directory's content from someone who has 7.4 on > Ubuntu 20.04 would fix my issue? > On Friday, November 25, 2022 at 4:53:06 p.m. UTC-4 alo...@gmail.com wrote: > >> You should completely ignore that suggestion and here is why ( >> https://github.com/kiprotect/klaro ). I think the issue you have is >> caused by how the migration from the Windows server to the Linux was done >> and is related to the handle server specifically because it's down. As a >> suggestion try to change one of the the items >> (e56a5422-b32b-4000-95dd-86467ef21c35) dc.identifier.uri from >> https://hdl.handle.net/your-handle-prefix/1916 to >> https://your-server-domain-name/handle/your-handle-prefix/1916 and try >> to access it and download it and see if that helps isolate the handle >> server is the cause. >> >> Hope It help. >> >> On Friday, November 25, 2022 at 10:20:58 PM UTC+3 Night Librarian wrote: >> >>> I had a suggestion to disable klaro to solve a downloading problem on my >>> DSpace 7.4, but I am not sure how to do that. Can someone give me a hint? >> >> -- 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/f5288c03-fea6-493a-941b-7db582a084a6n%40googlegroups.com.
[dspace-tech] Re: Dspace 7.4 backend pgcrypto extension not installed error
@Tim I hope you see this to fix/add an extra missing step to the
pgcrypto extention creation in the domcumentation so no user will face the
warning message Jeff posted if the user chose to create the extention on
the dspace database instead of adding it to a schema.
Executing psql --username=postgres dspace -c "CREATE EXTENSION pgcrypto;"
alone won't work unless the search_path is set to include the pgcrypto
extention in it.
# This should work
1) psql --username=postgres dspace -c "CREATE EXTENSION pgcrypto;"
2) psql --username=postgres dspace -c 'ALTER ROLE dspace IN DATABASE dspace
SET search_path = "$user",public,extensions,pgcrypto;'
3) psql --username=postgres dspace -c 'SHOW search_path;'
# Or this one
1) psql --username=postgres dspace -c "CREATE EXTENSION pgcrypto;"
2) psql --username=postgres dspace -c 'ALTER DATABASE dspace SET
search_path = "$user",public,extensions,pgcrypto;'
3) psql --username=postgres dspace -c 'SHOW search_path;'
# Or this one if the search path is set globally in the main postgresql
configuration file.
1) vi /path-to/postgresql.conf
search_path = '$user",public,extensions,pgcrypto'
# Or this one if the dspace script/scripts sets the search_path in them
(SET search_path = "$user",public,extensions,pgcrypto;).
1) psql --username=postgres dspace -c "CREATE EXTENSION pgcrypto;"
Trying to help.
On Sunday, December 4, 2022 at 4:26:32 AM UTC+3 Mohammad S. AlMutairi wrote:
> Hi Jeff,
>
> It is created but it can not be found because it's not included in the
> search path. One way of fixing this is to create a schema for all
> extensions first and then create the pgcrypto extension and add it to that
> schema. Just follow the steps you see below to pass the error.
>
> 1) su - postgres
> 2) createuser --username=postgres --no-superuser --pwprompt dspace
> 3) createdb --username=postgres --owner=dspace --encoding=UNICODE dspace
> 4) psql --username=postgres dspace
> 5) CREATE SCHEMA extensions;
> 6) CREATE EXTENSION pgcrypto SCHEMA extensions;
> 7) GRANT USAGE ON SCHEMA extensions TO dspace;
> 8) SELECT set_config('search_path',current_setting('search_path') ||
> ',extensions',false) WHERE current_setting('search_path') !~
> '(^|,)extensions(,|$)';
> 9) SHOW search_path;
> 10) ALTER DATABASE dspace SET search_path FROM CURRENT;
> 11) \q
> 12) exit
>
> Good luck
> On Friday, December 2, 2022 at 8:49:34 PM UTC+3 Jeff Mitchell wrote:
>
>> Just to clarify I had run this already and restarted PSQL as well before
>> running the build and install
>>
>> # Login to the database as a superuser, and enable the pgcrypto extension
>> on this database
>> psql --username=postgres dspace -c "CREATE EXTENSION pgcrypto;"
>> On Friday, December 2, 2022 at 11:19:20 AM UTC-6 Jeff Mitchell wrote:
>>
>>> Hello all,
>>>
>>> I just finished the build section of the configuration but when I got to
>>> run the ant fresh_install I get:
>>>
>>> [java] WARNING: Required PostgreSQL 'pgcrypto' extension is NOT
>>> INSTALLED on this database.
>>>
>>> [java]
>>> [java] ** DSpace REQUIRES PostgreSQL >= 9.4 AND pgcrypto extension
>>> >= 1.1 **
>>>
>>> However, when I check to see what extensions are installed it shows me
>>> that pgcrypto 1.3 is installed and yes I installed it as postgres and
>>> dspace db users. I'm running PSQL 13 if that helps.
>>>
>>> Thanks in advance!
>>>
>>> Jeff
>>>
>>>
--
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/7687d570-43e0-4a24-8a8c-40e13726e311n%40googlegroups.com.
[dspace-tech] How to display dc.description(en) or dc.description(es) depending on the interface language.
Hello everyone. I am new to Dspace. I am configuring DSpace to have a web with a bilingual interface (English, Spanish) Among other things, I have added the dc.description field, both for English and Spanish. When I navigate to the full item page, I see both fields: dc.description(en) and dc.description(es). When I navigate to the simple item page, I also see the two fields. However, on this page, the simple item page, I would like to see only the field that corresponds to the interface language. That is, if the interface at a given moment is in Spanish, I would like to see only the dc.description(es) field. However, if the interface at another time is in English, I'd like to see just the dc.description(en) field. I've been reading the documentation and I see that I can modify the structure of the simple item page by modifying the "untyped-item.component.html" file. There, I can add and remove fields, but how can I make it show only dc.description(en) or dc.description(es) depending on the interface language? Thank you very much. -- 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/efe8788a-4d89-4a26-8d5e-dba501245a59n%40googlegroups.com.
