From 8a69c29ace5c8656e917a725617c1f5668589398 Mon Sep 17 00:00:00 2001 From: UlfBj <38344769+UlfBj@users.noreply.github.com> Date: Fri, 22 Sep 2023 07:57:26 +0000 Subject: [PATCH] Auto-deploy docs built from commit b613169807a620165d67116ab55eb7822d59f8a8 --- 404.html | 16 +- build-system/index.html | 131 +++-- categories/index.html | 106 +++- client/index.html | 106 +++- datastore/index.html | 106 +++- feeder/index.html | 106 +++- images/fav.png | Bin 0 -> 1953 bytes images/vissv2.png | Bin 14154 -> 14301 bytes index.html | 122 +++-- index.json | 15 +- index.xml | 4 +- pocs/index.html | 106 +++- pocs/poc1/index.html | 106 +++- server/access-control-servers/index.html | 663 +++++++++++++++++++++++ server/access-control-servers/index.xml | 10 + server/index.html | 163 +++++- sitemap.xml | 2 + tags/index.html | 106 +++- 18 files changed, 1587 insertions(+), 281 deletions(-) create mode 100644 images/fav.png create mode 100644 server/access-control-servers/index.html create mode 100644 server/access-control-servers/index.xml diff --git a/404.html b/404.html index 04ca4b55..a4fabfb8 100644 --- a/404.html +++ b/404.html @@ -9,15 +9,15 @@ 404 Page not found - - - - - - - + + + + + + + - + + + + + + + + + +
+
+
+ +
+
+ + + + + + + + + + +
+
+ +
+
+ + +
+
+ +
+ +
+ +
+ +

+ + VISSv2 Access Control Servers +

+ + + + + + +

The VISSv2 access control model specifies two authorization servers:

+
    +
  • Access Grant server
    • +
  • Access Token server
    • +
+

Access Grant server

+

This server is in a typical scenario running in the cloud. It is built as a separate executable in the WAII/server/agt_server directory

+

$ go build

+

and run by

+

$ ./agt_server

+

It exposes an HTTP API according to the VISSv2 specification. However it is currently not TLS protected (which is a must in non-development scenario). +What is also missing in the AGS implementation is authentication of the client, which according to the specification should be an AGT task.

+

Access Token server

+

This server runs as a thread within the vissv2 server, so it is built by the vissv2 build command. +For it to be built, it is necessary to make sure that the “atServer” line in the serverComponents array in the vissv2server.go code is uncommented:

+
var serverComponents []string = []string{
+	"serviceMgr",
+	"httpMgr",
+	"wsMgr",
+	"mqttMgr",
+	"grpcMgr",
+	"atServer",
+}
+

If it is part of the vissv2server build, and if a VSS node is access control tagged, +the server will then forward the access token received in the client request to the ATS for validation.

+

The ATS will as part of the validation also use the VISSv2 specified policy documents if they are found in the working directory.

+

VISS web client submodule

+

This submodule implements a VISSv2 web client +that exposes a UI that is considerably more sophisticated than what other clients on the WAII repo exposes, +and it is particularly helpful when it comes to the client interactions with access control involved. +Check out the README on both repos for more information.

+ + + + + +
+ +
+ + +
+ + +
+ + + +
+ +
+
+
+ + + + + + + + + + + + + + + + + + + + diff --git a/server/access-control-servers/index.xml b/server/access-control-servers/index.xml new file mode 100644 index 00000000..e8083ca5 --- /dev/null +++ b/server/access-control-servers/index.xml @@ -0,0 +1,10 @@ + + + + VISSv2 Access Control Servers on W3C VISSv2 Reference Implementation + https://w3c.github.io/automotive-viss2/server/access-control-servers/ + Recent content in VISSv2 Access Control Servers on W3C VISSv2 Reference Implementation + Hugo -- gohugo.io + en-us + + diff --git a/server/index.html b/server/index.html index 59bc31f9..36d456e9 100644 --- a/server/index.html +++ b/server/index.html @@ -12,21 +12,21 @@ VISSv2 Server :: W3C VISSv2 Reference Implementation - - - - - - - - - + + + + + + + + + - + - +