Skip to content

Commit 47c51d0

Browse files
committed
linting
Signed-off-by: alexmerlin <alex.merlin.1985@gmail.com>
1 parent 370fd37 commit 47c51d0

1 file changed

Lines changed: 5 additions & 2 deletions

File tree

docs/book/v4/tutorials/token-authentication.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,8 +8,8 @@ and it consists of an alphanumeric string.
88

99
## How does it work?
1010

11-
In order to protect specific resources, clients need to be authenticated with user/admin roles. These roles are
12-
identified from the access token sent via the `Authorization` header.
11+
In order to protect specific resources, clients need to be authenticated with user/admin roles.
12+
These roles are identified from the access token sent via the `Authorization` header.
1313

1414
When DotKernel API receives a request, it tries to read the access token.
1515

@@ -26,9 +26,12 @@ Else, client's account is identified and client has `admin`/`user` role (the one
2626
DotKernel API provides out-of-the-box both an `admin` and a `user` account.
2727

2828
The admin account with **role** set to both `superuser` and `admin` with the following credentials:
29+
2930
- **identity**: `admin`
3031
- **password**: `dotkernel`
32+
3133
The user account with **role** set to both `user` and `guest` with the following credentials:
34+
3235
- **identify**: `test@dotkernel.com`
3336
- **password**: `dotkernel`
3437

0 commit comments

Comments
 (0)