Updated dependencies

vendor/github.com/docker/distribution/docs/spec/auth/index.md

@@ -1,8 +1,13 @@
----
-title: "Docker Registry Token Authentication"
-description: "Docker Registry v2 authentication schema"
-keywords: ["registry, on-prem, images, tags, repository, distribution, authentication, advanced"]
----
+<!--[metadata]>
++++
+title = "Docker Registry Token Authentication"
+description = "Docker Registry v2 authentication schema"
+keywords = ["registry, on-prem, images, tags, repository, distribution, authentication, advanced"]
+[menu.main]
+parent="smn_registry_ref"
+weight=100
++++
+<![end-metadata]-->
 
 # Docker Registry v2 authentication
 

vendor/github.com/docker/distribution/docs/spec/auth/jwt.md

@@ -1,8 +1,13 @@
----
-title: "Token Authentication Implementation"
-description: "Describe the reference implementation of the Docker Registry v2 authentication schema"
-keywords: ["registry, on-prem, images, tags, repository, distribution, JWT authentication, advanced"]
----
+<!--[metadata]>
++++
+title = "Token Authentication Implementation"
+description = "Describe the reference implementation of the Docker Registry v2 authentication schema"
+keywords = ["registry, on-prem, images, tags, repository, distribution, JWT authentication, advanced"]
+[menu.main]
+parent="smn_registry_ref"
+weight=101
++++
+<![end-metadata]-->
 
 # Docker Registry v2 Bearer token specification
 

vendor/github.com/docker/distribution/docs/spec/auth/oauth.md

@@ -1,8 +1,13 @@
----
-title: "Oauth2 Token Authentication"
-description: "Specifies the Docker Registry v2 authentication"
-keywords: ["registry, on-prem, images, tags, repository, distribution, oauth2, advanced"]
----
+<!--[metadata]>
++++
+title = "Oauth2 Token Authentication"
+description = "Specifies the Docker Registry v2 authentication"
+keywords = ["registry, on-prem, images, tags, repository, distribution, oauth2, advanced"]
+[menu.main]
+parent="smn_registry_ref"
+weight=102
++++
+<![end-metadata]-->
 
 # Docker Registry v2 authentication using OAuth2
 
@@ -188,3 +193,4 @@ Content-Type: application/json
 
 {"refresh_token":"kas9Da81Dfa8","access_token":"eyJhbGciOiJFUzI1NiIsInR5":"expires_in":900,"scope":"repository:samalba/my-app:pull,repository:samalba/my-app:push"}
 ```
+

vendor/github.com/docker/distribution/docs/spec/auth/scope.md

@@ -1,8 +1,13 @@
----
-title: "Token Scope Documentation"
-description: "Describes the scope and access fields used for registry authorization tokens"
-keywords: ["registry, on-prem, images, tags, repository, distribution, advanced, access, scope"]
----
+<!--[metadata]>
++++
+title = "Token Scope Documentation"
+description = "Describes the scope and access fields used for registry authorization tokens"
+keywords = ["registry, on-prem, images, tags, repository, distribution, advanced, access, scope"]
+[menu.main]
+parent="smn_registry_ref"
+weight=103
++++
+<![end-metadata]-->
 
 # Docker Registry Token Scope and Access
 
@@ -39,23 +44,13 @@ intended to represent. This type may be specific to a resource provider but must
 be understood by the authorization server in order to validate the subject
 is authorized for a specific resource.
 
-#### Resource Class
-
-The resource type might have a resource class which further classifies the
-the resource name within the resource type. A class is not required and
-is specific to the resource type.
-
 #### Example Resource Types
 
  - `repository` - represents a single repository within a registry. A
 repository may represent many manifest or content blobs, but the resource type
 is considered the collections of those items. Actions which may be performed on
 a `repository` are `pull` for accessing the collection and `push` for adding to
-it. By default the `repository` type has the class of `image`.
- - `repository(plugin)` - represents a single repository of plugins within a
-registry. A plugin repository has the same content and actions as a repository.
- - `registry` - represents the entire registry. Used for administrative actions
-or lookup operations that span an entire registry.
+it.
 
 ### Resource Name
 
@@ -88,8 +83,7 @@ scopes.
 ```
 scope                   := resourcescope [ ' ' resourcescope ]*
 resourcescope           := resourcetype  ":" resourcename  ":" action [ ',' action ]*
-resourcetype            := resourcetypevalue [ '(' resourcetypevalue ')' ]
-resourcetypevalue       := /[a-z0-9]+/
+resourcetype            := /[a-z]*/
 resourcename            := [ hostname '/' ] component [ '/' component ]*
 hostname                := hostcomponent ['.' hostcomponent]* [':' port-number]
 hostcomponent           := /([a-zA-Z0-9]|[a-zA-Z0-9][a-zA-Z0-9-]*[a-zA-Z0-9])/
@@ -146,3 +140,4 @@ done by fetching an access token using the refresh token. Since the refresh
 token is not scoped to specific resources for an audience, extra care should
 be taken to only use the refresh token to negotiate new access tokens directly
 with the authorization server, and never with a resource provider.
+

vendor/github.com/docker/distribution/docs/spec/auth/token.md

@@ -1,8 +1,13 @@
----
-title: "Token Authentication Specification"
-description: "Specifies the Docker Registry v2 authentication"
-keywords: ["registry, on-prem, images, tags, repository, distribution, Bearer authentication, advanced"]
----
+<!--[metadata]>
++++
+title = "Token Authentication Specification"
+description = "Specifies the Docker Registry v2 authentication"
+keywords = ["registry, on-prem, images, tags, repository, distribution, Bearer authentication, advanced"]
+[menu.main]
+parent="smn_registry_ref"
+weight=104
++++
+<![end-metadata]-->
 
 # Docker Registry v2 authentication via central service
 
@@ -20,7 +25,7 @@ This document outlines the v2 Docker registry authentication scheme:
 5. The client retries the original request with the Bearer token embedded in
    the request's Authorization header.
 6. The Registry authorizes the client by validating the Bearer token and the
-   claim set embedded within it and begins the push/pull session as usual.
+   claim set embedded within it and begins the push/pull session as usual. 
 
 ## Requirements
 
@@ -156,7 +161,7 @@ Defines getting a bearer and refresh token using the token endpoint.
         <code>expires_in</code>
     </dt>
     <dd>
-        (Optional) The duration in seconds since the token was issued that it
+        (Optional) The duration in seconds since the token was issued that it 
         will remain valid.  When omitted, this defaults to 60 seconds.  For
         compatibility with older clients, a token should never be returned with
         less than 60 seconds to live.