Code Monkey home page Code Monkey logo

Comments (6)

dustin-decker avatar dustin-decker commented on August 29, 2024

I think the proposed solution is a good trade-off of security for reliability. There will certainly be blips in availability of the API in the future. There is definitely lower hanging fruit than the update+DOS attack.

from rbacsync.

stevvooe avatar stevvooe commented on August 29, 2024

Thanks for the report!

Another possibility for a fix would be a cache to protect against momentary upstream unavailability. We can have it stay operational for a period then eventually timeout the cache.

I also feel like we should report the recency of group updates on the status field of the config objects so that it can be monitored.

from rbacsync.

dilyevsky avatar dilyevsky commented on August 29, 2024

For discoverability, the error that was reported by RBACSync pod:

Event(v1.ObjectReference{Kind:"RBACSyncConfig", Namespace:"default", Name:"namespace-bindings", UID:"b76e9626-0255-11e9-bfd1", APIVersion:"rbacsync.example.com/v1alpha", ResourceVersion:"37596907", FieldPath:""}): type: 'Warning' reason: 'BindingError' group [email protected] lookup failed: unknown error fetching group members: googleapi: Error 403: Not Authorized to access this resource/api, forbidden

from rbacsync.

stevvooe avatar stevvooe commented on August 29, 2024

Do we have a proposed error behavior for the set of error codes? We need to differentiate permanent errors from temporary access errors. For example, what would be the behavior of a 404 vs a 403? Are there are cases where the upstream wants to remove access to the group information and have that reflected in rbacsync? We don't want to create cases where we can't control the behavior.

from rbacsync.

stevvooe avatar stevvooe commented on August 29, 2024

Note that we saw this behavior under timeouts, as well:

Event(v1.ObjectReference{Kind:"RBACSyncConfig", Namespace:"default", Name:"namespace-bindings", UID:"ff3f6641-0253-11e9-9985-42010ad4000b", APIVersion:"rbacsync.getcruise.com/v1alpha", ResourceVersion:"34555077", FieldPath:""}): type: 'Warning' reason: 'BindingError' group [email protected] lookup failed: unknown error fetching group members: context deadline exceeded

from rbacsync.

stevvooe avatar stevvooe commented on August 29, 2024

Closed by #14.

from rbacsync.

Related Issues (9)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.