External Auth ~ish

[didierofrivia]

This huge PR addresses part of #58 ... However, all the previous PRs pointing to this branch were thoroughly reviewed (?).

Even if we are only certifying that Rate Limiting works, it's prepared for Auth too. We will close the issue when we provide documentation and deliver it along proper integration tests

List of the main PRs:

• Refactoring for external auth. Vol I #64
• Move attribute parsing to attribute trait #65
• Refactoring for external auth. Vol II #66
• Integration development environment #67
• Add initial implementation of auth service #69
• Operation dispatcher FSM #77
• Setup services from configuration #78
• On grpc response flow #81
• Process auth CheckResponse #86
• Refactor pluginconfig #87
• Refactoring operation dispatcher #90
• Simplifying Operation state transition and exec of req msg #91

Config example

---
extensions:
  limitador:
    type: ratelimit
    endpoint: limitador-cluster
    failureMode: deny
policies:
  - name: rlp-ns-A/rlp-name-A
    hostnames:
      - '*.toystore.com'
      - example.com
    rules:
     - conditions:
          - allOf:
              - selector: request.path
                operator: eq
                value: /admin/toy
              - selector: request.method
                operator: eq
                value: POST
              - selector: request.host
                operator: eq
                value: cars.toystore.com
      actions:
        - extension: limitador
          scope: rlp-ns-A/rlp-name-A
          data:
            - static:
                key: rlp-ns-A/rlp-name-A
                value: "1"
            - selector:
                selector: auth.metadata.username

Verification:

Use the new guide in the README to verify multi-action setup:

make build && make local-setup

Port-forward envoy and watch the logs for all services:

kubectl port-forward --namespace default deployment/envoy 8000:8000
kubectl logs -f deployment/envoy
kubectl logs -f deployment/authorino
kubectl logs -f deployment/limitador

Test the authenticated rate limiting:

curl -H "Host: test.a.multi.com" http://127.0.0.1:8000/get -i
# HTTP/1.1 401 Unauthorized

Alice has 5 requests per 10 seconds:

while :; do curl --write-out '%{http_code}\n' --silent --output /dev/null -H "Authorization: APIKEY IAMALICE" -H "Host: test.a.multi.com" http://127.0.0.1:8000/get | grep -E --color "\b(429)\b|$"; sleep 1; done

Bob has 2 requests per 10 seconds:

while :; do curl --write-out '%{http_code}\n' --silent --output /dev/null -H "Authorization: APIKEY IAMBOB" -H "Host: test.a.multi.com" http://127.0.0.1:8000/get | grep -E --color "\b(429)\b|$"; sleep 1; done

[gitguardian]

⚠️ GitGuardian has uncovered 4 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
13357796	Triggered	Generic High Entropy Secret	8dd4c97	utils/deploy/authconfig.yaml	View secret
13357796	Triggered	Generic High Entropy Secret	40ce002	utils/deploy/authconfig.yaml	View secret
13357796	Triggered	Generic High Entropy Secret	91da443	utils/deploy/authconfig.yaml	View secret
13357796	Triggered	Generic High Entropy Secret	88cb14b	utils/deploy/authconfig.yaml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[eguzki]

Have you considered in squashing commits? Is it worth 72 commits? Up to you.

[eguzki]

This example is outdated

[adam-cattermole]

Lgtm