#Idle Relationships

1 messages · Page 1 of 1 (latest)

tribal juniper
#

Hello @idle steeple ,

Firstly, when the model changes, the relations that changed along with the model will become invalid because they cannot be invoked with the new model.

For example, consider this model:

entity user{}

entity organization {
    relation owner @user
}

Here, the relationship could be:

organization:1#owner@user:1

When you change this model to:

entity user{}

entity organization {
    relation member @user
}

Since there is no 'owner' relationship in the new model, it won't be accepted in the check query. In this case, the previous relationship:

organization:1#owner@user:1

will become idle. Of course, if you delete these relationships before changing the model and utilize our Garbage Collector feature, you will achieve better performance.

#

An issue similar to the one you've mentioned has been opened, and it's currently under review:

https://github.com/Permify/permify/issues/576

Once we add it to our roadmap, I'll be able to inform you about a specific timeline or due date.

GitHub

Feature Add ability to model and bundle relations (tuples). Problem It is currently responsibility of the services to model how relations are created and deleted when actions happen on resources. H...

#

Idle Relationships

tribal juniper
#

Currently, we don't have an article on this topic, but there are some authentication integrations in our roadmap.

  • Okta
  • Auth0
  • AWS Cognito
  • Active Directory
  • One Login
  • Ping Identity

What's your identity and authentication provider we could easily add to our roadmap? If you'd like, I can also notify you when it's published.

idle steeple
#

Hey @tribal juniper, Thanks for very brief response. It actually helped me understand alot of questions I had.

So, regarding Authentication and Authorization, just trying to understand and evaluate the tool at a Production Scale using ReBAC.

Looking forward on Authentication and Relationship Bundles updates 🙂