<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
Hi Stian,
<div class=""><br class="">
</div>
<div class="">I understand. And typically this would indeed by what you want. However in our specific case groups are not part of our realm data as such but belong to our run-time data and are managed in exactly the same way as our users, role mappings and
group mappings. But I guess you cannot cater for all needs so it’s ok.</div>
<div class=""><br class="">
</div>
<div class="">Another, probably related thing, is that with the LDAP group synching (using the user federation group mapper) groups synched from LDAP to Keycloak are never removed from Keycloak. When a group is deleted from LDAP and the sync is done again the
group remains in Keycloak. Not what you want but I guess the issue is that Keycloak cannot make the distinction between a group synched from LDAP versus a group created from Keycloak itself? The LDAP group mapping is set up quite different from the user synching
of course.</div>
<div class=""><br class="">
</div>
<div class="">cheers</div>
<div class=""><br class="">
<div>
<blockquote type="cite" class="">
<div class="">On 02 Mar 2016, at 13:25, Stian Thorgersen <<a href="mailto:sthorger@redhat.com" class="">sthorger@redhat.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div dir="ltr" class="">Roles and groups should be exported to the realm export, while role mappings and group mappings should be exported to the user export.</div>
<div class="gmail_extra"><br class="">
<div class="gmail_quote">On 2 March 2016 at 13:15, Edgar Vonk - <a href="http://info.nl" class="">
Info.nl</a> <span dir="ltr" class=""><<a href="mailto:Edgar@info.nl" target="_blank" class="">Edgar@info.nl</a>></span> wrote:<br class="">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br class="">
<br class="">
We notice that when we export our custom realm to a JSON file (to a directory) that this file also contains all User Groups. We do not want this as we synchronise these User Groups from AD/LDAP just like our users. We want to have realm configuration in the
realm JSON file only and not any ‘run-time’ managed data such as users and user groups.<br class="">
<br class="">
Currently only users are exported to a different JSON file (<a href="http://keycloak.github.io/docs/userguide/keycloak-server/html/export-import.html" rel="noreferrer" target="_blank" class="">http://keycloak.github.io/docs/userguide/keycloak-server/html/export-import.html</a>)
but groups are not. Does it make sense to create a feature request to also export user groups separately?<br class="">
<br class="">
We have hundreds of groups in AD/LDAP which we sync to Keycloak so we really do not want these in the realm JSON.<br class="">
<br class="">
cheers<br class="">
<br class="">
Edgar<br class="">
<br class="">
_______________________________________________<br class="">
keycloak-user mailing list<br class="">
<a href="mailto:keycloak-user@lists.jboss.org" class="">keycloak-user@lists.jboss.org</a><br class="">
<a href="https://lists.jboss.org/mailman/listinfo/keycloak-user" rel="noreferrer" target="_blank" class="">https://lists.jboss.org/mailman/listinfo/keycloak-user</a></blockquote>
</div>
<br class="">
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</body>
</html>