Can we export/import an individual client to and from the ClientRepresentation format? This will be crucial for debugging problems in support cases. -- Bill Burke JBoss, a division of Red Hat http://bill.burkecentral.com _______________________________________________ keycloak-dev mailing list keycloak-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/keycloak-dev

I added https://issues.jboss.org/browse/KEYCLOAK-2420. We should try to get this included for 1.9. Should be pretty trivial to do.

On 1 February 2016 at 10:39, Stian Thorgersen <sthorger(a)redhat.com <mailto:sthorger@redhat.com>> wrote: +1 We can import already, but we should add export of individual client On 30 January 2016 at 15:18, Bill Burke <bburke(a)redhat.com <mailto:bburke@redhat.com>> wrote: Can we export/import an individual client to and from the ClientRepresentation format? This will be crucial for debugging problems in support cases. -- Bill Burke JBoss, a division of Red Hat http://bill.burkecentral.com _______________________________________________ keycloak-dev mailing list keycloak-dev(a)lists.jboss.org <mailto:keycloak-dev@lists.jboss.org> https://lists.jboss.org/mailman/listinfo/keycloak-dev _______________________________________________ keycloak-dev mailing list keycloak-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/keycloak-dev

On 1 February 2016 at 14:45, Stan Silvert <ssilvert(a)redhat.com <mailto:ssilvert@redhat.com>> wrote: On 2/1/2016 4:40 AM, Stian Thorgersen wrote: > I added https://issues.jboss.org/browse/KEYCLOAK-2420. We should > try to get this included for 1.9. Should be pretty trivial to do. I already implemented a version of this for several of the resources but we left it out in favor of eventually having a single-screen solution. I could dig it out and add it for clients. It's not partial export we want - it's just export of a single client.

> > On 1 February 2016 at 10:39, Stian Thorgersen > <sthorger(a)redhat.com <mailto:sthorger@redhat.com>> wrote: > > +1 We can import already, but we should add export of > individual client > > On 30 January 2016 at 15:18, Bill Burke <bburke(a)redhat.com > <mailto:bburke@redhat.com>> wrote: > > Can we export/import an individual client to and from the > ClientRepresentation format? This will be crucial for > debugging > problems in support cases. > > -- > Bill Burke > JBoss, a division of Red Hat > http://bill.burkecentral.com > > _______________________________________________ > keycloak-dev mailing list > keycloak-dev(a)lists.jboss.org > <mailto:keycloak-dev@lists.jboss.org> > https://lists.jboss.org/mailman/listinfo/keycloak-dev > > > > > > _______________________________________________ > keycloak-dev mailing list > keycloak-dev(a)lists.jboss.org <mailto:keycloak-dev@lists.jboss.org> > https://lists.jboss.org/mailman/listinfo/keycloak-dev _______________________________________________ keycloak-dev mailing list keycloak-dev(a)lists.jboss.org <mailto:keycloak-dev@lists.jboss.org> https://lists.jboss.org/mailman/listinfo/keycloak-dev

On 1 February 2016 at 15:02, Stan Silvert <ssilvert(a)redhat.com <mailto:ssilvert@redhat.com>> wrote: On 2/1/2016 8:53 AM, Stian Thorgersen wrote: > > > On 1 February 2016 at 14:45, Stan Silvert <ssilvert(a)redhat.com > <mailto:ssilvert@redhat.com>> wrote: > > On 2/1/2016 4:40 AM, Stian Thorgersen wrote: >> I added https://issues.jboss.org/browse/KEYCLOAK-2420. We >> should try to get this included for 1.9. Should be pretty >> trivial to do. > I already implemented a version of this for several of the > resources but we left it out in favor of eventually having a > single-screen solution. I could dig it out and add it for > clients. > > > It's not partial export we want - it's just export of a single > client. That's what the old implementation would do. Export a single client?

> >> >> On 1 February 2016 at 10:39, Stian Thorgersen >> <sthorger(a)redhat.com <mailto:sthorger@redhat.com>> wrote: >> >> +1 We can import already, but we should add export of >> individual client >> >> On 30 January 2016 at 15:18, Bill Burke >> <bburke(a)redhat.com <mailto:bburke@redhat.com>> wrote: >> >> Can we export/import an individual client to and >> from the >> ClientRepresentation format? This will be crucial >> for debugging >> problems in support cases. >> >> -- >> Bill Burke >> JBoss, a division of Red Hat >> http://bill.burkecentral.com >> >> _______________________________________________ >> keycloak-dev mailing list >> keycloak-dev(a)lists.jboss.org >> <mailto:keycloak-dev@lists.jboss.org> >> https://lists.jboss.org/mailman/listinfo/keycloak-dev >> >> >> >> >> >> _______________________________________________ >> keycloak-dev mailing list >> keycloak-dev(a)lists.jboss.org <mailto:keycloak-dev@lists.jboss.org> >> https://lists.jboss.org/mailman/listinfo/keycloak-dev > > > _______________________________________________ > keycloak-dev mailing list > keycloak-dev(a)lists.jboss.org > <mailto:keycloak-dev@lists.jboss.org> > https://lists.jboss.org/mailman/listinfo/keycloak-dev > >

On 1 February 2016 at 15:26, Stan Silvert <ssilvert(a)redhat.com <mailto:ssilvert@redhat.com>> wrote: On 2/1/2016 9:23 AM, Stian Thorgersen wrote: > > > On 1 February 2016 at 15:02, Stan Silvert <ssilvert(a)redhat.com > <mailto:ssilvert@redhat.com>> wrote: > > On 2/1/2016 8:53 AM, Stian Thorgersen wrote: >> >> >> On 1 February 2016 at 14:45, Stan Silvert >> <ssilvert(a)redhat.com <mailto:ssilvert@redhat.com>> wrote: >> >> On 2/1/2016 4:40 AM, Stian Thorgersen wrote: >>> I added https://issues.jboss.org/browse/KEYCLOAK-2420. >>> We should try to get this included for 1.9. Should be >>> pretty trivial to do. >> I already implemented a version of this for several of >> the resources but we left it out in favor of eventually >> having a single-screen solution. I could dig it out and >> add it for clients. >> >> >> It's not partial export we want - it's just export of a >> single client. > That's what the old implementation would do. > > > Export a single client? Yes. To be more specific, it allowed you to filter the output so you could export a single client or a subset of all clients. I could easily adapt this to export the client you are viewing. The advantage is that I already implemented all the code that does this and it allows you to save it on the server or on the admin's machine. That's not what we want. We don't actually need any server side code for this feature. The client json is already available from the server all we need is an export button that downloads it as a json file.

On 1 February 2016 at 15:37, Bill Burke <bburke(a)redhat.com <mailto:bburke@redhat.com>> wrote: On 2/1/2016 9:31 AM, Stian Thorgersen wrote: > > > On 1 February 2016 at 15:26, Stan Silvert <ssilvert(a)redhat.com > <mailto:ssilvert@redhat.com>> wrote: > > On 2/1/2016 9:23 AM, Stian Thorgersen wrote: >> >> >> On 1 February 2016 at 15:02, Stan Silvert >> <ssilvert(a)redhat.com <mailto:ssilvert@redhat.com>> wrote: >> >> On 2/1/2016 8:53 AM, Stian Thorgersen wrote: >>> >>> >>> On 1 February 2016 at 14:45, Stan Silvert >>> <ssilvert(a)redhat.com <mailto:ssilvert@redhat.com>> wrote: >>> >>> On 2/1/2016 4:40 AM, Stian Thorgersen wrote: >>>> I added >>>> https://issues.jboss.org/browse/KEYCLOAK-2420. We >>>> should try to get this included for 1.9. Should be >>>> pretty trivial to do. >>> I already implemented a version of this for several >>> of the resources but we left it out in favor of >>> eventually having a single-screen solution. I >>> could dig it out and add it for clients. >>> >>> >>> It's not partial export we want - it's just export of a >>> single client. >> That's what the old implementation would do. >> >> >> Export a single client? > Yes. To be more specific, it allowed you to filter the > output so you could export a single client or a subset of all > clients. > > I could easily adapt this to export the client you are > viewing. The advantage is that I already implemented all the > code that does this and it allows you to save it on the > server or on the admin's machine. > > > That's not what we want. We don't actually need any server side > code for this feature. The client json is already available from > the server all we need is an export button that downloads it as a > json file. Just an export button on the client list page. next to each client just like we already have edit/delete. Is it not better to have the button on the client detail page?