Skip to content

Commit

Permalink
docs: fix links in authorization doc
Browse files Browse the repository at this point in the history
Some relative links were not formatted properly; clicking
them didn't work. They are working now.
  • Loading branch information
emonddr committed Feb 6, 2020
1 parent 499356f commit 7dc1c70
Showing 1 changed file with 6 additions and 6 deletions.
12 changes: 6 additions & 6 deletions docs/site/Loopback-component-authorization.md
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,7 @@ necessary privileges/access rights by using the permissions annotated by the

The expectations from various stake holders (LoopBack, Architects, Developers)
for implementation of the authorization features are given below in the
[Chain of Responsibility](##Chain-of-Responsibility) section.
[Chain of Responsibility](#chain-of-responsibility) section.

## Chain of Responsibility

Expand Down Expand Up @@ -104,9 +104,9 @@ class.
```

- The authorization `options` are provided specifically for enforcing the
[decision matrix](##Authorization-by-decision-matrix), which is used to
combine voters from all `authorize` functions. The options are described per
the interface AuthorizationOptions.
[decision matrix](#authorization-by-decision-matrix), which is used to combine
voters from all `authorize` functions. The options are described per the
interface AuthorizationOptions.

```ts
export interface AuthorizationOptions {
Expand Down Expand Up @@ -159,7 +159,7 @@ The `Authorization interceptor` enforces authorization with user-provided
collects `voters` provided in the `@authorize` decorator of the endpoint.
- It executes each of the above collected functions provided by the user.
- Based on the result of all functions it enforces access/privilege control
using [a decision matrix](##Authorization-by-decision-matrix).
using [a decision matrix](#authorization-by-decision-matrix).

## Configuring API Endpoints

Expand Down Expand Up @@ -346,7 +346,7 @@ corresponding options.
- if the `authorizer` function returns `ALLOW`, but voter 1 in authorize
decorator returns `ABSTAIN` and voter 2 in decorator returns `DENY`.
- In this case, if the options provided while
[registering the authorization component](#Authorization-Component),
[registering the authorization component](#authorization-component),
provides precedence as `DENY`, then the access for the subject is denied to
the endpoint.

Expand Down

0 comments on commit 7dc1c70

Please sign in to comment.