vbatts/registry
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

fix type of keywords entry in frontmatter (in /registry/) (#517)

Browse source 
keywords should be a string, not an array containing one string

Signed-off-by: Gaetan de Villele <gdevillele@gmail.com>
This commit is contained in:
Gaetan 2016-11-10 11:54:25 -08:00 • committed by John Mulhausen
parent bc1e162172
commit cc71bedafb
33 changed files with 68 additions and 101 deletions
Download patch file Download diff file Expand all files Collapse all files

5
docs/spec/auth/index.md
View file

@ -1,11 +1,10 @@
---
description: Docker Registry v2 authentication schema
keywords:
- registry, on-prem, images, tags, repository, distribution, authentication, advanced
keywords: registry, on-prem, images, tags, repository, distribution, authentication, advanced
title: Docker Registry v2 authentication
---
See the [Token Authentication Specification](token.md),
[Token Authentication Implementation](jwt.md),
[Token Scope Documentation](scope.md),
[OAuth2 Token Authentication](oauth.md) for more information.
[OAuth2 Token Authentication](oauth.md) for more information.

5
docs/spec/auth/jwt.md
View file

@ -1,7 +1,6 @@
---
description: Describe the reference implementation of the Docker Registry v2 authentication schema
keywords:
- registry, on-prem, images, tags, repository, distribution, JWT authentication, advanced
keywords: registry, on-prem, images, tags, repository, distribution, JWT authentication, advanced
title: Docker Registry v2 Bearer token specification
---
@ -325,4 +324,4 @@ authorization then the registry will return the appropriate error.
At no point in this process should the registry need to call back to the
authorization server. The registry only needs to be supplied with the trusted
public keys to verify the token signatures.
public keys to verify the token signatures.

5
docs/spec/auth/oauth.md
View file

@ -1,7 +1,6 @@
---
description: Specifies the Docker Registry v2 authentication
keywords:
- registry, on-prem, images, tags, repository, distribution, oauth2, advanced
keywords: registry, on-prem, images, tags, repository, distribution, oauth2, advanced
title: Docker Registry v2 authentication using OAuth2
---
@ -181,4 +180,4 @@ HTTP/1.1 200 OK
Content-Type: application/json
{"refresh_token":"kas9Da81Dfa8","access_token":"eyJhbGciOiJFUzI1NiIsInR5":"expires_in":900,"scope":"repository:samalba/my-app:pull,repository:samalba/my-app:push"}
```
```

5
docs/spec/auth/scope.md
View file

@ -1,7 +1,6 @@
---
description: Describes the scope and access fields used for registry authorization tokens
keywords:
- registry, on-prem, images, tags, repository, distribution, advanced, access, scope
keywords: registry, on-prem, images, tags, repository, distribution, advanced, access, scope
title: Docker Registry token scope and access
---
@ -133,4 +132,4 @@ restricting scope to specific type, name, and actions combinations should be
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.
with the authorization server, and never with a resource provider.

5
docs/spec/auth/token.md
View file

@ -1,7 +1,6 @@
---
description: Specifies the Docker Registry v2 authentication
keywords:
- registry, on-prem, images, tags, repository, distribution, Bearer authentication, advanced
keywords: registry, on-prem, images, tags, repository, distribution, Bearer authentication, advanced
title: Docker Registry v2 authentication via central service
---
@ -248,4 +247,4 @@ Authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJFUzI1NiIsImtpZCI6IkJWM0Q6MkFWWj
```
This is also described in [Section 2.1 of RFC 6750: The OAuth 2.0 Authorization
Framework: Bearer Token Usage](https://tools.ietf.org/html/rfc6750#section-2.1)
Framework: Bearer Token Usage](https://tools.ietf.org/html/rfc6750#section-2.1)