mirror of
https://github.com/fosrl/docs-v2.git
synced 2026-02-08 05:56:45 +00:00
more typos
This commit is contained in:
@@ -33,5 +33,5 @@ Device approvals are enabled on a per-role basis. To enable device approvals for
|
||||
Once enabled, any new user connecting with that role will require approval from an administrator before it can access organization resources.
|
||||
|
||||
<Tip>
|
||||
You can not enable device approvals for the "Admin" role.
|
||||
You cannot enable device approvals for the "Admin" role.
|
||||
</Tip>
|
||||
@@ -17,7 +17,7 @@ Request logs capture every HTTP request that passes through Pangolin's reverse p
|
||||
- Troubleshooting connectivity and routing issues
|
||||
|
||||
<Frame>
|
||||
<img src="/images/request_logs.png"centered/>
|
||||
<img src="/images/request_logs.png" centered/>
|
||||
</Frame>
|
||||
|
||||
## Request Log Fields
|
||||
|
||||
@@ -63,7 +63,7 @@ pangolin apply blueprint --file /path/to/blueprint.yaml
|
||||
|
||||
You can also apply blueprints directly through the Pangolin API with an API key. [Take a look at the API documentation for more details.](https://api.pangolin.net/v1/docs/#/Organization/put_org__orgId__blueprint)
|
||||
|
||||
PUT to `/org/{orgId}/blueprint` with a base64 encodes JSON body like the following:
|
||||
PUT to `/org/{orgId}/blueprint` with a base64 encoded JSON body like the following:
|
||||
|
||||
```json
|
||||
{
|
||||
|
||||
@@ -5,7 +5,7 @@ description: "Learn how to use Pangolin's REST API to automate and script operat
|
||||
---
|
||||
|
||||
<Warning>
|
||||
Pangolin is in heavy development. The REST API routes and behavior may include braking changes between updates. We will do our best to document large changes.
|
||||
Pangolin is in heavy development. The REST API routes and behavior may include breaking changes between updates. We will do our best to document large changes.
|
||||
</Warning>
|
||||
|
||||
The API is REST-based and supports many operations available through the web interface. Authentication uses Bearer tokens, and you can create multiple API keys with specific permissions for different use cases.
|
||||
|
||||
@@ -3,7 +3,7 @@ title: "Understanding Resources"
|
||||
description: "Resources are any network address you want to make available to users"
|
||||
---
|
||||
|
||||
Resources respresent the applications, hosts, or ranges you make available for remote access to users. Resources exist on the remote networks of your sites. Users only ever think about connecting to resources and not specific sites.
|
||||
Resources represent the applications, hosts, or ranges you make available for remote access to users. Resources exist on the remote networks of your sites. Users only ever think about connecting to resources and not specific sites.
|
||||
|
||||
By default, no resources are made available on sites. Admins must define resources with backend targets, and assign specific access policies before any users can gain access.
|
||||
|
||||
@@ -20,7 +20,7 @@ There are two types of resources: public resources and private resources.
|
||||
|
||||
<Card title="Private Resources">
|
||||
- Zero-trust VPN
|
||||
- Access to every resources requires authentication
|
||||
- Access to every resource requires authentication
|
||||
- Users and machines access when connected with a client
|
||||
</Card>
|
||||
</CardGroup>
|
||||
|
||||
Reference in New Issue
Block a user