{% include navmenu.html %}
In this exercise, we will note the additional capabilities that are enabled by authenticating as a DSpace user in Postman.
To illustrate the process, we will step through the authentication process manually.
Use the URL and credentials in the footer of this page.
Note: Postman does provide a mechanism to script authentication.
api/authn/status
In the return section, note that authentication is false.
Note that the credentials you need to use will differ from the screenshot below.
Note that the login endpoint should be invoked with the POST method.
POST api/authn/login
api/authn/status
In the return section, note that authentication is true.
As long as you continue to use the tab that contains this Bearer token, you will continue to be authenticated. If the Bearer token times out, repeat the steps above to generate a new one.
Rerun the queries that you ran in Exercise 2. Note the result count.
api/discover/search/objects
api/discover/search/objects?query=research
How does this compare to your unauthenticated results?
You can verify this by running the same query in a different tab (without the Bearer token) and note the difference in counts.
It is possible to create and delete objects through Postman.
In this process, you will perform the underlying tasks that the DSpace Angular client will perform on behalf of a user.
POST api/submission/workspaceitems
This endpoint allows you to post an empty object to the request.
Note the id of the object that is created.
GET api/submission/workspaceitems/[id]
Note the error section where missing mandatory metadata and sections are listed
DELETE api/submission/workspaceitems/[id]
GET api/submission/workspaceitems/[id]
{% include credentials.html %} {% include nav.html %}