Dan HeathandRobin Beck
22a9074724
* docs: Update meta content - Concepts * docs: Revisions * Update website/content/docs/concepts/domain-model/credentials.mdx Co-authored-by: Robin Beck <stellarsquall@users.noreply.github.com> * Update website/content/docs/concepts/domain-model/scopes.mdx Co-authored-by: Robin Beck <stellarsquall@users.noreply.github.com> * docs: Update exec flag description * Update website/content/docs/concepts/filtering/events.mdx Co-authored-by: Robin Beck <stellarsquall@users.noreply.github.com> * docs: Update domain model descriptions * docs: Update domain model titles * docs: Edits for consistency --------- Co-authored-by: Robin Beck <stellarsquall@users.noreply.github.com>
28 lines
1.0 KiB
Plaintext
28 lines
1.0 KiB
Plaintext
---
|
|
layout: docs
|
|
page_title: Session connection resource
|
|
description: >-
|
|
Learn how the session connection resource represents the proxy Boundary creates between user and host. Understand how connections are established and terminated.
|
|
---
|
|
|
|
# Session connections
|
|
|
|
A session connection represents an authorized proxy between a [user][] and a [host][]. After the creation of a
|
|
[session][], a user initiates a connection to a [target][] using the Boundary-provided
|
|
proxy information and [credentials][] (if applicable).
|
|
|
|
Users can create multiple connections to a [target][], so long as the [session][] has not expired or reached its maximum
|
|
number of connections.
|
|
|
|
Session connections terminate on user exit from the proxy, or on termination of the [session][].
|
|
|
|
## Referenced by
|
|
|
|
- [Session][]
|
|
|
|
[credentials]: /boundary/docs/concepts/domain-model/credentials
|
|
[host]: /boundary/docs/concepts/domain-model/hosts
|
|
[session]: /boundary/docs/concepts/domain-model/sessions
|
|
[target]: /boundary/docs/concepts/domain-model/targets
|
|
[user]: /boundary/docs/concepts/domain-model/users
|