Skip to content

Commit

Permalink
docs: Microservice authentication using E2EE approval (#1316)
Browse files Browse the repository at this point in the history
Closes #613

Signed-off-by: Bryon Nevis <bryon.nevis@intel.com>
  • Loading branch information
bnevis-i authored Dec 11, 2023
1 parent d2fa22c commit bc469fd
Show file tree
Hide file tree
Showing 4 changed files with 5 additions and 3 deletions.
3 changes: 2 additions & 1 deletion docs_src/design/TOC.md
Original file line number Diff line number Diff line change
Expand Up @@ -51,4 +51,5 @@
| [0025 Record and Replay](./adr/application/0025-Record-and-Replay.md) | Record data from various devices and play data back without devices present |
| [0026 Common Configuration](./adr/0026-Common Configuration.md) | Separate out the common configuration setting into a single source for all the services |
| [0027 URIs for Files](./adr/0027-URIs for Files.md) | Add capability to load service files from remote locations using URIs |
| [0028 Microservice communication security](./adr/security/0028-authentication.md) | Microservice communication security / authentication (token-based) |
| [0028 Microservice communication security (token)](./adr/security/0028-authentication.md) | Microservice communication security / authentication (token-based) |
| [0029 Microservice communication security (E2EE)](./adr/security/0029-authentication.md) | Microservice communication security / authentication (end-to-end authentication) |
File renamed without changes
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,7 @@
## Change Log

- [proposed](https://github.com/edgexfoundry/edgex-docs/pull/935) (2023-01-28)
- [approved](https://github.com/edgexfoundry/edgex-docs/pull/1316) (2023-12-09)

## Referenced Use Case(s)

Expand All @@ -20,7 +21,7 @@ The AS-IS Architecture figure below depicts the current state of
microservice communication security as of EdgeX 3.0,
when security is enabled:

![AS-IS Architecture](tbd-as-is.jpg)
![AS-IS Architecture](0029-as-is.jpg)

As shown in the diagram,
EdgeX 3.0 components are secured as follows:
Expand Down Expand Up @@ -104,7 +105,7 @@ API gateway traffic onto the zero-trust network on the backend.

The new TO-BE architecture is diagrammed in the following figure:

![TO-BE Architecture](tbd-to-be.jpg)
![TO-BE Architecture](0029-to-be.jpg)

This diagram conveys a lot of information in little space.
A little exposition on what this diagram is intending to show:
Expand Down
File renamed without changes

0 comments on commit bc469fd

Please sign in to comment.