Skip to content

[v14] docs: Add Docker to MSFT teams plugin #33387

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lsgunn-teleport merged 1 commit into from
Oct 17, 2023
Merged

[v14] docs: Add Docker to MSFT teams plugin #33387

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 14 additions & 6 deletions docs/pages/access-controls/access-request-plugins/ssh-approval-msteams.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -162,7 +162,7 @@ credentials and generate the Teams App package that will be used to install the
Microsoft Teams App. You will also configure the plugin to notify
the right Microsoft Teams users when it receives an Access Request update.

### Generate a config file and assets
### Generate a configuration file and assets

Generate a configuration file for the plugin. The instructions depend on whether
you are deploying the plugin on a virtual machine or Kubernetes:
Expand Down Expand Up @@ -232,7 +232,7 @@ application UUID with each execution. It is not possible to use an `app.zip` and
a TOML configuration generated by two different executions.
</Admonition>

### Edit the config file
### Edit the configuration file

Edit the configuration file according to the instructions below.

Expand All @@ -246,7 +246,7 @@ cluster.
#### `[msapi]`/`msTeams`

<Tabs>
<TabItem label="Executable">
<TabItem label="Executable or Docker">

Make sure the `app_id`, `app_secret`, `tenant_id`, and `teams_app_id` fields are
filled in with the correct information, which you obtained earlier in this
Expand All @@ -269,7 +269,7 @@ look up the role being requested and identify the Microsoft Teams users and chan
notify.

<Tabs>
<TabItem label="Executable">
<TabItem label="Executable or Docker">

Here is an example of a `role_to_recipients` map:

Expand Down Expand Up @@ -328,7 +328,7 @@ by adding the following to your `role_to_recipients` config (replace
role earlier):

<Tabs>
<TabItem label="Executable">
<TabItem label="Executable or Docker">

```toml
[role_to_recipients]
Expand All @@ -349,7 +349,7 @@ roleToRecipients:
The final configuration file should resemble the following:

<Tabs>
<TabItem label="Executable">
<TabItem label="Executable or Docker">
```toml
(!examples/resources/plugins/teleport-msteams.toml!)
```
Expand Down Expand Up @@ -457,6 +457,14 @@ DEBU Watcher connected watcherjob/watcherjob.go:121
INFO Plugin is ready msteams/app.go:227
```

</TabItem>
<TabItem label="Docker">
Run the plugin:

```code
$ docker run -v <path-to-config>:/etc/teleport-msteams.toml public.ecr.aws/gravitational/teleport-plugin-msteams:(=teleport.version=) start
```

</TabItem>
<TabItem label="Helm Chart">
Install the plugin:
Expand Down