10:46 a.m.
Hi,
I was trying to update the owner of an existing resource with
resource.setOwner(newOwnerId);
getAuthzClient().protection().resource().update(resource);
There is no Exception, but it seems that resource still keeps the previous owner... is
there a different way to achieve this? Is it possible at all?
thanks
gianni
PS: the server is keycloak 4.8.3Final
7:40 a.m.
Hi,
You can't update the owner. Are you trying to change ownership ? Couldn't
you share or set permissions that allow access to some other user ?
Regards.
Pedro Igor
On Sat, Feb 23, 2019 at 1:48 PM Gianni <giannif.libero.it(a)gmail.com> wrote:
Hi,
I was trying to update the owner of an existing resource with
resource.setOwner(newOwnerId);
getAuthzClient().protection().resource().update(resource);
There is no Exception, but it seems that resource still keeps the previous
owner... is there a different way to achieve this? Is it possible at all?
thanks
gianni
PS: the server is keycloak 4.8.3Final
_______________________________________________
keycloak-user mailing list
keycloak-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user
12:58 a.m.
Thanks for the prompt feedback.
Yes, I was trying to change ownership. Allowing access using a policy was my backup plan
too :) but it doesn’t fully fit all use-cases, in my view. For example in the case an
employee who is the owner of resources leaves the company (or changes department and he’s
no longer in charge of those resources) one might want to change ownership.
Just out of curiosity, is there any technical constraint not to allow change of
ownership?
Thanks again and with best regards
gianni
On 25 Feb 2019, at 14:40, Pedro Igor Silva <psilva(a)redhat.com>
wrote:
Hi,
You can't update the owner. Are you trying to change ownership ? Couldn't you
share or set permissions that allow access to some other user ?
Regards.
Pedro Igor
On Sat, Feb 23, 2019 at 1:48 PM Gianni <giannif.libero.it(a)gmail.com
<mailto:giannif.libero.it@gmail.com>> wrote:
Hi,
I was trying to update the owner of an existing resource with
resource.setOwner(newOwnerId);
getAuthzClient().protection().resource().update(resource);
There is no Exception, but it seems that resource still keeps the previous owner... is
there a different way to achieve this? Is it possible at all?
thanks
gianni
PS: the server is keycloak 4.8.3Final
_______________________________________________
keycloak-user mailing list
keycloak-user(a)lists.jboss.org <mailto:keycloak-user@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/keycloak-user
<https://lists.jboss.org/mailman/listinfo/keycloak-user>
2143
days inactive
2146
days old
2 comments
2 participants
participants (2)
-
Gianni -
Pedro Igor Silva