Skip to content

Commit 8c5ed4b

Browse files
committed
Fix continuity of ordered list - Authentication OAuth implicit flow
For reference: [Adding Elements in Lists](https://www.markdownguide.org/basic-syntax/#adding-elements-in-lists) The Jekyll docs link directly out to markdownguide.org.
1 parent e6018bb commit 8c5ed4b

1 file changed

Lines changed: 6 additions & 6 deletions

File tree

content/v2/overview/authentication.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -53,17 +53,17 @@ With the client id, authentication and API access can proceed as follows using a
5353

5454
1. Client Application initiates browser access to SCF authentication endpoint
5555

56-
<pre class="terminal">
57-
https://seeclickfix.com/oauth/authorize?client_id=YOUR_CLIENT_ID&redirect_uri=YOUR_REDIRECT_URI&response_type=token
58-
</pre>
56+
<pre class="terminal">
57+
https://seeclickfix.com/oauth/authorize?client_id=YOUR_CLIENT_ID&redirect_uri=YOUR_REDIRECT_URI&response_type=token
58+
</pre>
5959

6060
2. SCF user enters SCF credentials and on success is redirected to Client Application Redirect URI which will include an access_token
6161

6262
3. Client Application can now make API requests on behalf of the user, by including user's access token. See [RFC 6750](http://tools.ietf.org/html/rfc6750#section-2.1) for options and detail for transmitting the access token to the API endpoints. One method is to send the access_token in the `Authentication` header:
6363

64-
<pre class="terminal">
65-
Authentication: Bearer xxxxxxxxxxxxxxxxxxxx
66-
</pre>
64+
<pre class="terminal">
65+
Authentication: Bearer xxxxxxxxxxxxxxxxxxxx
66+
</pre>
6767

6868
For more details see this [overview](https://auth0.com/docs/flows/concepts/implicit) of the implicit flow [RFC 6749, section 4.2](https://tools.ietf.org/html/rfc6749#section-4.2)
6969

0 commit comments

Comments
 (0)