spec: add 401 unauthorized error (#43)

Add 401 error model so the server can differentiate between AnthN errors
(401) and AuthZ errors (403)

Author: jackye1995

java/lance-catalog-apache-client/api/openapi.yaml

@@ -45,6 +45,8 @@ paths:
           $ref: '#/components/responses/ListNamespacesResponse'
         "400":
           $ref: '#/components/responses/BadRequestErrorResponse'
+        "401":
+          $ref: '#/components/responses/UnauthorizedResponse'
         "403":
           $ref: '#/components/responses/ForbiddenResponse'
         "406":
@@ -72,6 +74,8 @@ paths:
           $ref: '#/components/responses/CreateNamespaceResponse'
         "400":
           $ref: '#/components/responses/BadRequestErrorResponse'
+        "401":
+          $ref: '#/components/responses/UnauthorizedResponse'
         "403":
           $ref: '#/components/responses/ForbiddenResponse'
         "406":
@@ -100,6 +104,8 @@ paths:
           description: "Success, no content"
         "400":
           $ref: '#/components/responses/BadRequestErrorResponse'
+        "401":
+          $ref: '#/components/responses/UnauthorizedResponse'
         "403":
           $ref: '#/components/responses/ForbiddenResponse'
         "404":
@@ -123,6 +129,8 @@ paths:
           $ref: '#/components/responses/GetNamespaceResponse'
         "400":
           $ref: '#/components/responses/BadRequestErrorResponse'
+        "401":
+          $ref: '#/components/responses/UnauthorizedResponse'
         "403":
           $ref: '#/components/responses/ForbiddenResponse'
         "404":
@@ -146,6 +154,8 @@ paths:
           description: "Success, no content"
         "400":
           $ref: '#/components/responses/BadRequestErrorResponse'
+        "401":
+          $ref: '#/components/responses/UnauthorizedResponse'
         "403":
           $ref: '#/components/responses/ForbiddenResponse'
         "404":
@@ -231,6 +241,19 @@ components:
         \ request body format or other forms of request validation failure, such as\
         \ invalid json. Usually serves application/json content, although in some\
         \ cases simple text/plain content might be returned by the server's middleware."
+    UnauthorizedResponse:
+      content:
+        application/json:
+          example:
+            type: /errors/unauthorized-request
+            title: No valid authentication credentials for the operation
+            status: 401
+            detail: ""
+            instance: /v1/namespaces
+          schema:
+            $ref: '#/components/schemas/ErrorModel'
+      description: Unauthorized. The request lacks valid authentication credentials
+        for the operation.
     ForbiddenResponse:
       content:
         application/json:

java/lance-catalog-apache-client/docs/NamespaceApi.md

@@ -75,6 +75,7 @@ No authorization required
 |-------------|-------------|------------------|
 | **200** | Represents a successful call to create a namespace. Returns the namespace created, as well as any properties that were stored for the namespace, including those the server might have added. Implementations are not required to support namespace properties. |  -  |
 | **400** | Indicates a bad request error. It could be caused by an unexpected request body format or other forms of request validation failure, such as invalid json. Usually serves application/json content, although in some cases simple text/plain content might be returned by the server's middleware. |  -  |
+| **401** | Unauthorized. The request lacks valid authentication credentials for the operation. |  -  |
 | **403** | Forbidden. Authenticated user does not have the necessary permissions. |  -  |
 | **406** | Not Acceptable / Unsupported Operation. The server does not support this operation. |  -  |
 | **503** | The service is not ready to handle the request. The client should wait and retry. The service may additionally send a Retry-After header to indicate when to retry. |  -  |
@@ -143,6 +144,7 @@ No authorization required
 |-------------|-------------|------------------|
 | **204** | Success, no content |  -  |
 | **400** | Indicates a bad request error. It could be caused by an unexpected request body format or other forms of request validation failure, such as invalid json. Usually serves application/json content, although in some cases simple text/plain content might be returned by the server's middleware. |  -  |
+| **401** | Unauthorized. The request lacks valid authentication credentials for the operation. |  -  |
 | **403** | Forbidden. Authenticated user does not have the necessary permissions. |  -  |
 | **404** | A server-side problem that means can not find the specified resource. |  -  |
 | **503** | The service is not ready to handle the request. The client should wait and retry. The service may additionally send a Retry-After header to indicate when to retry. |  -  |
@@ -214,6 +216,7 @@ No authorization required
 |-------------|-------------|------------------|
 | **200** | Returns a namespace, as well as any properties stored on the namespace if namespace properties are supported by the server. |  -  |
 | **400** | Indicates a bad request error. It could be caused by an unexpected request body format or other forms of request validation failure, such as invalid json. Usually serves application/json content, although in some cases simple text/plain content might be returned by the server's middleware. |  -  |
+| **401** | Unauthorized. The request lacks valid authentication credentials for the operation. |  -  |
 | **403** | Forbidden. Authenticated user does not have the necessary permissions. |  -  |
 | **404** | A server-side problem that means can not find the specified resource. |  -  |
 | **503** | The service is not ready to handle the request. The client should wait and retry. The service may additionally send a Retry-After header to indicate when to retry. |  -  |
@@ -279,6 +282,7 @@ No authorization required
 |-------------|-------------|------------------|
 | **200** | A list of namespaces |  -  |
 | **400** | Indicates a bad request error. It could be caused by an unexpected request body format or other forms of request validation failure, such as invalid json. Usually serves application/json content, although in some cases simple text/plain content might be returned by the server's middleware. |  -  |
+| **401** | Unauthorized. The request lacks valid authentication credentials for the operation. |  -  |
 | **403** | Forbidden. Authenticated user does not have the necessary permissions. |  -  |
 | **406** | Not Acceptable / Unsupported Operation. The server does not support this operation. |  -  |
 | **503** | The service is not ready to handle the request. The client should wait and retry. The service may additionally send a Retry-After header to indicate when to retry. |  -  |
@@ -349,6 +353,7 @@ No authorization required
 |-------------|-------------|------------------|
 | **200** | Success, no content |  -  |
 | **400** | Indicates a bad request error. It could be caused by an unexpected request body format or other forms of request validation failure, such as invalid json. Usually serves application/json content, although in some cases simple text/plain content might be returned by the server's middleware. |  -  |
+| **401** | Unauthorized. The request lacks valid authentication credentials for the operation. |  -  |
 | **403** | Forbidden. Authenticated user does not have the necessary permissions. |  -  |
 | **404** | A server-side problem that means can not find the specified resource. |  -  |
 | **503** | The service is not ready to handle the request. The client should wait and retry. The service may additionally send a Retry-After header to indicate when to retry. |  -  |