mirror of
https://github.com/seaweedfs/seaweedfs.git
synced 2024-01-19 02:48:24 +00:00
10404c4275
- one JWT for reading and one for writing, analogous to how the JWT between Master and Volume Server works - I did not implement IP `whiteList` parameter on the filer Additionally, because http_util.DownloadFile now sets the JWT, the `download` command should now work when `jwt.signing.read` is configured. By looking at the code, I think this case did not work before. ## Docs to be adjusted after a release Page `Amazon-S3-API`: ``` # Authentication with Filer You can use mTLS for the gRPC connection between S3-API-Proxy and the filer, as explained in [Security-Configuration](Security-Configuration) - controlled by the `grpc.*` configuration in `security.toml`. Starting with version XX, it is also possible to authenticate the HTTP operations between the S3-API-Proxy and the Filer (especially uploading new files). This is configured by setting `filer_jwt.signing.key` and `filer_jwt.signing.read.key` in `security.toml`. With both configurations (gRPC and JWT), it is possible to have Filer and S3 communicate in fully authenticated fashion; so Filer will reject any unauthenticated communication. ``` Page `Security Overview`: ``` The following items are not covered, yet: - master server http REST services Starting with version XX, the Filer HTTP REST services can be secured with a JWT, by setting `filer_jwt.signing.key` and `filer_jwt.signing.read.key` in `security.toml`. ... Before version XX: "weed filer -disableHttp", disable http operations, only gRPC operations are allowed. This works with "weed mount" by FUSE. It does **not work** with the [S3 Gateway](Amazon S3 API), as this does HTTP calls to the Filer. Starting with version XX: secured by JWT, by setting `filer_jwt.signing.key` and `filer_jwt.signing.read.key` in `security.toml`. **This now works with the [S3 Gateway](Amazon S3 API).** ... # Securing Filer HTTP with JWT To enable JWT-based access control for the Filer, 1. generate `security.toml` file by `weed scaffold -config=security` 2. set `filer_jwt.signing.key` to a secret string - and optionally filer_jwt.signing.read.key` as well to a secret string 3. copy the same `security.toml` file to the filers and all S3 proxies. If `filer_jwt.signing.key` is configured: When sending upload/update/delete HTTP operations to a filer server, the request header `Authorization` should be the JWT string (`Authorization: Bearer [JwtToken]`). The operation is authorized after the filer validates the JWT with `filer_jwt.signing.key`. If `filer_jwt.signing.read.key` is configured: When sending GET or HEAD requests to a filer server, the request header `Authorization` should be the JWT string (`Authorization: Bearer [JwtToken]`). The operation is authorized after the filer validates the JWT with `filer_jwt.signing.read.key`. The S3 API Gateway reads the above JWT keys and sends authenticated HTTP requests to the filer. ``` Page `Security Configuration`: ``` (update scaffold file) ... [filer_jwt.signing] key = "blahblahblahblah" [filer_jwt.signing.read] key = "blahblahblahblah" ``` Resolves: #158 |
||
|---|---|---|
| .. | ||
| http | ||
| policy | ||
| s3_constants | ||
| s3err | ||
| AmazonS3.xsd | ||
| auth_credentials.go | ||
| auth_credentials_subscribe.go | ||
| auth_credentials_test.go | ||
| auth_signature_v2.go | ||
| auth_signature_v4.go | ||
| auto_signature_v4_test.go | ||
| chunked_reader_v4.go | ||
| custom_types.go | ||
| filer_multipart.go | ||
| filer_multipart_test.go | ||
| filer_util.go | ||
| filer_util_tags.go | ||
| README.txt | ||
| s3api_auth.go | ||
| s3api_bucket_handlers.go | ||
| s3api_bucket_handlers_test.go | ||
| s3api_handlers.go | ||
| s3api_object_copy_handlers.go | ||
| s3api_object_handlers.go | ||
| s3api_object_handlers_postpolicy.go | ||
| s3api_object_multipart_handlers.go | ||
| s3api_object_skip_handlers.go | ||
| s3api_object_tagging_handlers.go | ||
| s3api_objects_list_handlers.go | ||
| s3api_objects_list_handlers_test.go | ||
| s3api_policy.go | ||
| s3api_server.go | ||
| s3api_status_handlers.go | ||
| s3api_test.go | ||
| s3api_xsd_generated.go | ||
| stats.go | ||
| tags.go | ||
| tags_test.go | ||
see https://blog.aqwari.net/xml-schema-go/ 1. go get aqwari.net/xml/cmd/xsdgen 2. xsdgen -o s3api_xsd_generated.go -pkg s3api AmazonS3.xsd