Hmm I tried following the instructions on the page by running: docker-compose
-f docker-compose.yml -f docker-compose-cli.yml pull
But then running: docker-compose -f docker-compose.yml -f
docker-compose-cli.yml build
Gave the error below:
.
.
.
#25 1802.9 [INFO] Compiling 44 source files to
/app/dspace-iiif/target/classes
#25 4187.4 Killed
------
failed to solve: rpc error: code = Unknown desc = executor failed running
[/bin/sh -c mvn package -Pdspace-rest && mv
/app/dspace/target/${TARGET_DIR}/* /install && mvn clean]: exit code: 137
On Monday, December 20, 2021 at 7:59:11 AM UTC-7 DSpace Technical Support
wrote:
> Hi Jack,
>
> Unfortunately, because our Demo site allows anyone administrative
> privileges, it looks like someone has modified our usual Demo Site
> Administrator account to no longer have full Admin privileges. We noticed
> this recently as well, and we're working on pushing an update to the demo
> site to revert it back to the default content & user accounts, likely later
> this week.
>
> In the meantime, if you need to do testing more immediately, I'd highly
> recommend using our DSpace 7 Docker images, which you can install locally.
> We also have a test/demo data set you can easily install, which includes
> the same demo user accounts & content from api7.dspace.org. See the
> instructions at
> https://github.com/DSpace/DSpace/blob/main/dspace/src/main/docker-compose/README.md
>
> Tim
>
> On Saturday, December 18, 2021 at 6:05:33 PM UTC-6 Jack Peplinski wrote:
>
>> I'm trying to develop an application for Dspace and I was testing out
>> some requests in Postman.
>>
>> I check my authorization token was ok using the /authn/status endpoint
>> with the curl request:
>> curl --location --request GET '
>> https://api7.dspace.org/server/api/authn/status' \
>> --header 'Authorization: Bearer {token}'
>>
>> This returned:
>> {
>> "id": null,
>> "okay": true,
>> "authenticated": true,
>> "type": "status",
>> "_links": {
>> "eperson": {
>> "href": "
>> https://api7.dspace.org/server/api/eperson/epersons/9bff97a3-1f6f-4690-a554-d2d099851062
>> "
>> },
>> "self": {
>> "href": "https://api7.dspace.org/server/api/authn/status";
>> }
>> }
>> }
>>
>> But when I went to use the /core/items endpoint with the curl request:
>> curl --location --request GET '
>> https://api7.dspace.org/server/api/core/items' \
>> --header 'Authorization: Bearer {token}'
>>
>> This returned:
>> {
>> "timestamp": "2021-12-18T23:48:15.468+00:00",
>> "status": 403,
>> "error": "Forbidden",
>> "message": "Access is denied",
>> "path": "/server/api/core/items"
>> }
>>
>> Did I do something wrong or is the account I used, [email protected],
>> just not have permissions for this endpoint? If the latter is the case, is
>> there a user account that I can use this endpoint for on the
>> api7.dspace.org demo site.
>>
>
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/dspace-tech/3ba55495-0996-43b2-b519-533d22fb3982n%40googlegroups.com.
