Skip to content

Conversation

@taniwha3
Copy link
Contributor

Signed-off-by: Tani <111664369+taniwha3@users.noreply.github.com>
@@ -0,0 +1,71 @@
# Design / Feature

*TODO for the document:*
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I should include a section about observability here.

Signed-off-by: Tani <111664369+taniwha3@users.noreply.github.com>
Signed-off-by: Tani <111664369+taniwha3@users.noreply.github.com>

Authorization decisions default to deny.

Not installing a policy engine causes all requests to be denied.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We must must have "reasonable defaults" and opinions. Its a key part of the project.

Is this our reasonable default? Or should we give the user a default policy engine?

- changes to the policy do not require a recompilation of auraed.
- policy can be centralized for multiple auraed.

### Goals
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We will need to bake both authn and authz into our standard library, or at the very least call it out of scope.

  • Do we have an authn subsystem? Or is this "transparent" based on the aurae.toml?
  • Do we have an authz subsystem? Or is this "transparent" based on the aurae.toml?

More on subsystems: https://github.com/aurae-runtime/api/tree/main/spec#aurae-api-specification

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants