<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">Hi,</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">Thanks for the fast answer. I totally understand the permissions issue, and well, the reason to send the previous mail was just to avoid this kind of problems.</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">Regarding to your suggestion on how to implement the self-registration, I understand (after reading the documentation again) how to use the Realm Resource SPI together with user attributes or either use the Client Registration Service.</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">However, as I see, there is no way to integrate it with the existing UI that Keycloak has,doesn’t it? I’ve only been able to find that there are ways to extend the ServerInfo page with some information, (example found in chapter 4.1.1 in the documentation). Is there anything similar to a FormAction as described in 34.5.1 in the documentation to integrate this extension with Keycloak’s UI, or I should create my own UI to create the interface for this custom endpoints?</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">I’m sorry if this questions may be a bit basic, but even with the documentation, as it is so extensive, I get sometimes a bit lost on what tools I have available to implement with in this platform.</div> <br> <div id="bloop_sign_1465304608582738944" class="bloop_sign"><div style="font-family:helvetica,arial;font-size:13px">— </div><div style="font-family:helvetica,arial;font-size:13px">Best Regards, </div><div style="font-family:helvetica,arial;font-size:13px"><br>Erik Berdonces Bonelo<br></div></div> <br><p class="airmail_on">On 6 June 2016 at 19:36:07, Stian Thorgersen (<a href="mailto:sthorger@redhat.com">sthorger@redhat.com</a>) wrote:</p> <blockquote type="cite" class="clean_bq"><span><div><div></div><div>
<title></title>
<div dir="ltr">Hi,
<div><br></div>
<div>We are planing to add more fine-grained permissions on admin
endpoints in the future, but it will be a while until we get to it.
I'm not very keen on accepting something like this now as we are
planning to do fairly big changes around this in the future. You're
also the first person to ask about having clients specific to user,
other people have so far requested groups of clients that groups of
users can manage.</div>
<div><br></div>
<div>I'd recommend using the Realm Resource SPI to create custom
endpoints to accomplish this. You can use an attribute on the
clients to store the user that has created the client and only
allow that user to modify it in the future. You can also consider
using the client registration service. The client registration
service allows anyone with a create-role or an initial access token
to create clients. When a client is created it returns a
registration access token that gives permission to modify/delete
that particular client in the future.</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On 6 June 2016 at 14:39, Erik Berdonces
Bonelo <span dir="ltr"><<a href="mailto:e.berdoncesbonelo@campus.tu-berlin.de" target="_blank">e.berdoncesbonelo@campus.tu-berlin.de</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
Hello,<br>
<br>
I’m working at the moment in a Master Thesis project in TU Berlin
where we are using Keycloak for Authentication and Authorisation
purposes.<br>
We are planning on extending Keycloak in order to provide users a
way to register clients/applications by themselves into the
platform, while having an admin overseeing the system.<br>
<br>
This would mean that as a user, if I have the proper rights I
should be able to create and manage my own clients. With, this it
comes the idea of ownership, as this would mean that a client
ownership could be transferred to someone else.<br>
Also, the admin should be able to accept, revoke and delete the
clients and requests to create clients in my Keycloak.<br>
<br>
At the moment the only option would be giving the permission to
create clients to the user, but that would allow to change ANY of
the possible clients.<br>
<br>
Then, I have two questions:<br>
1. Would it make sense to integrate this to the Keycloak
core?<br>
2. If it doesn’t make sense to merge it in the core, is
there any plugin system to extend Keycloak’s core? I’ve seen a
discussion related to a plugin system in GitHub but there is no
outcome yet. We would rather like to integrate it with Keycloak
itself, otherwise the other option would be creating a client that
uses Keycloak’s REST API to manage the clients remotely.<br>
<br>
Thanks a lot in advance! <br>
<br>
— <br>
Best Regards,<br>
Erik Berdonces Bonelo<br>
<br>
<br>
_______________________________________________<br>
keycloak-dev mailing list<br>
<a href="mailto:keycloak-dev@lists.jboss.org">keycloak-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/keycloak-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/keycloak-dev</a></blockquote>
</div>
<br></div>
</div></div></span></blockquote></body></html>