Replies: 1 comment 2 replies
-
The attributes within the IdP (in this case Keycloak) do not specifically drive access. The way we derive access control is through entitlement. Entitlement is handled through Subject Mappings where by the user is referred to as the subject. The CLI is the best way to manage your subject mappings unless you want to draft your own gRPC requests. https://github.com/opentdf/otdfctl |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have an instance of the platform and Keycloak installed and I have provisioned Keycloak from the service and that ran with no issues. I am attempting to encrypt and decrypt using the examples within the project but not having much luck:
As far as I can tell, this just takes a string value and the rest of the defaults should be fine.
Also, is there any documentation on how the user attributes in Keycloak are used to control the ABAC decisions for granting decryption? From what I can see, the client uses the Client/secret credentials in Keycloak, but attributes are associated with users in Keycloak. There must be some way to joint these two entities together in a manageable way?
Beta Was this translation helpful? Give feedback.
All reactions