- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 26 for Action (0.19 sec)
-
docs/multi-user/README.md
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Tue Mar 21 06:38:06 GMT 2023 - 8K bytes - Viewed (0) -
docs/sts/custom-token-identity.md
| Parameter | Type | Required | | |-----------------|---------|----------|----------------------------------------------------------------------| | Action | String | Yes | Value must be `AssumeRoleWithCustomToken` | | Version | String | Yes | Value must be `2011-06-15` |
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Fri May 27 00:58:09 GMT 2022 - 3K bytes - Viewed (0) -
docs/sts/tls.md
``` export MINIO_IDENTITY_TLS_ENABLE=on ``` ## Example MinIO exposes a custom S3 STS API endpoint as `Action=AssumeRoleWithCertificate`. A client has to send an HTTP `POST` request to `https://<host>:<port>?Action=AssumeRoleWithCertificate&Version=2011-06-15`. Since the authentication and authorization happens via X.509 certificates the client has to send the request over **TLS** and has to provide
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Sep 29 04:28:45 GMT 2022 - 6K bytes - Viewed (0) -
docs/metrics/prometheus/README.md
metrics_path: /minio/v2/metrics/resource scheme: http static_configs: - targets: ['localhost:9000'] ``` ### 4. Update `scrape_configs` section in prometheus.yml To authorize every scrape request, copy and paste the generated `scrape_configs` section in the prometheus.yml and restart the Prometheus service. ### 5. Start Prometheus Start (or) Restart Prometheus service by running ```sh
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Fri Apr 12 15:49:30 GMT 2024 - 7.1K bytes - Viewed (0) -
docs/tls/kubernetes/README.md
## 3. Update deployment yaml file Whether you are planning to use Kubernetes StatefulSet or Kubernetes Deployment, the steps remain the same. If you're using certificates provided by a CA, add the below section in your yaml file under `spec.volumes[]` ```yaml volumes: - name: secret-volume secret: secretName: tls-ssl-minio items: - key: public.crt
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Sep 29 04:28:45 GMT 2022 - 3K bytes - Viewed (0) -
docs/kms/README.md
The main difference between various MinIO-KMS deployments is the KMS implementation. The following table helps you select the right option for your use case: | KMS | Purpose |
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Jan 18 07:03:17 GMT 2024 - 7.1K bytes - Viewed (0) -
docs/iam/opa.md
```sh cat > example.rego <<EOF package httpapi.authz import input default allow = false # Allow the root user to perform any action. allow { input.owner == true } # All other users may do anything other than call PutObject allow { input.action != "s3:PutObject" input.owner == false } EOF ``` Then load the policy via OPA's REST API. ``` curl -X PUT --data-binary @example.rego \
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Sun Jul 17 15:43:14 GMT 2022 - 2.3K bytes - Viewed (0) -
docs/sts/assume-role.md
## Sample `POST` Request ``` http://minio:9000/?Action=AssumeRole&DurationSeconds=3600&Version=2011-06-15&Policy={"Version":"2012-10-17","Statement":[{"Sid":"Stmt1","Effect":"Allow","Action":"s3:*","Resource":"arn:aws:s3:::*"}]}&AUTHPARAMS ``` ## Sample Response ``` <?xml version="1.0" encoding="UTF-8"?>
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Sep 29 04:28:45 GMT 2022 - 7.1K bytes - Viewed (0) -
docs/sts/wso2.md
- Navigate to service provider section, expand Inbound Authentication Configurations and expand OAuth/OpenID Connect Configuration. - Copy the OAuth Client Key as the value for `<CLIENT_ID>`. - Copy the OAuth Client Secret as the value for `<CLIENT_SECRET>`.
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Sep 29 04:28:45 GMT 2022 - 8.7K bytes - Viewed (0) -
docs/ftp/README.md
******@****.*** arcfour256 arcfour128 arcfour aes128-cbc 3des-cbc ``` `--sftp=mac-algos=...` specifies a default set of MAC algorithms in preference order. This is based on RFC 4253, section 6.4, but with hmac-md5 variants removed because they have reached the end of their useful life. Valid values: ``` ******@****.*** ******@****.*** hmac-sha2-256
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Tue Apr 30 15:15:45 GMT 2024 - 7.1K bytes - Viewed (0)