Skip to content

Latest commit

 

History

History
99 lines (56 loc) · 3.13 KB

exercise2.md

File metadata and controls

99 lines (56 loc) · 3.13 KB
Raw

{% include navmenu.html %}

Exercise 2: Authenticating with the HAL Browser

1. Searching for objects in an unauthenticated session

In this step, you will run a couple of DSpace discovery searches before authenticating and note the result counts.

1a. Search for all objects and note the result count

api/discover/search/objects

1b. Search for "research" and note the result count

api/discover/search/objects?query=research

After authenticating, you will see how the results change.

2. Authentication status

2a. Using the authn endpoint, view your authentication status

api/authn/status

In the response body, note the status

authenticated: false

2b. From the authn endpoint, POST to the login method

For convenience, the HAL browser provides a login box at the top of the page.
Click "Login" and supply the credentials at the bottom of this page.

Behind the scenes, the login box will perform the following operation.

POST api/auth/login

This action will return a response header named "Authorization" which contains an authorization token.
The HAL browser will pass this token in subsequent requests.

When we use Postman, you will see this process in more detail.

2c. Verify your authentication status.

api/authn/status

The response body should now include the following status.

authenticated: true

Note: this authentication token will eventually expire. Repeat step 1b if you need a new token.

For the rest of this exercise, the steps will make use of this authentication token.

3. View non-public content

Note how these counts differ from your prior results.

3a. Search for all objects and note the result count

api/discover/search/objects

3b. Try again to access the items endpoint

In exercise 1 you have verified that access to the items endpoint was forbidden to unauthorized user, now that you are loggedin as administrator what do you see? How many items are listed? how this number compare with the items exposed over the browse endpoints?

api/core/items

4. EPersons and Groups

Explore other endpoints restricted to administrators

4a. View all EPersons

Use the HAL Browser to view all people (epersons) known to the repository.

api/eperson/epersons

4b. View a specific EPerson

Use the HAL Browser to view the data for a specific user (eperson).

api/eperson/epersons/[uuid]

4c. View all Groups

Use the HAL Browser to view all user groups known to the repository.

api/eperson/groups

4d. View a specific Group

Use the HAL Browser to view the data for a specific user group.

api/eperson/groups/[uuid]

5. Next steps

The HAL browser does not yet pass authentication status to requests that modify data, so this exercise will stop here.

As the DSpace REST code evolves, more Create/Update/Delete functionality will become available through the HAL browser.

Note: the exclamation point in the HAL Browser is the mechanism that will be used to invoke POST/DELETE/PUT operations. The question mark is used when the link declare parameter via templating, the ALPS support will add more granular control over that.

{% include credentials.html %} {% include nav.html %}