Maybe, there's two separate needs one is for us to be able to showcase
Keycloak and the other is for folks to be able to try out Keycloak. One
solution that fits all could be great. If we have a single click install
that let's folk play with all aspects including LDAP/Kerberos that could be
great.
On 19 January 2017 at 03:06, Bruno Oliveira <bruno(a)abstractj.org> wrote:
Do you mean something related to this
https://issues.jboss.org/
browse/KEYCLOAK-3577 ?
On 2017-01-18, Stian Thorgersen wrote:
> Forgot to mention that in addition to the quickstarts we should have a
demo
> bundle. It would replace the "demo" bits as well as the demo
distribution.
> Probably based on Docker images.
>
> Something that with one click can get a full blown demo to showcase
> Keycloak up and running.
>
> On 18 January 2017 at 16:33, Stian Thorgersen <sthorger(a)redhat.com>
wrote:
>
> > Here's my take on it.
> >
> > "demo" bits (everything in demo-template) should be replaced with
the
new
> > quickstarts format. Some of these are already redundant (service, jsp,
> > html5).
> >
> > Authz - Pedro is working on RHSSO quickstart / migration
> >
> > Fuse - Marek is working on RHSSO quickstart / migration
> >
> > Broker - These needs some updating as they don't work and are not even
> > included in example DL. Not sure how important these are though.
> >
> > The rest I would put at the following priorities:
> >
> > P1:
> > Cordova
> > Themes
> > Cors (maybe the existing quickstarts i.e. services should have
explanation
> > on how to configure CORS instead)
> > SAML - maybe they should be updated to follow new quickstart format
> >
> > P2:
> > JS Console
> > Kerberos
> > LDAP
> > Providers
> > Admin client
> >
> > P3:
> > Multi tenant
> > Basic auth
> >
> >
> >
> > On 18 January 2017 at 15:36, Sebastien Blanc <sblanc(a)redhat.com>
wrote:
> >
> >> Hi !
> >>
> >> We have our new quickstart repo but we still have our "old"
examples
> >> folder
> >> containing a lot of samples (more than 50!). While most of them are
> >> relevant, we still need to look if all of them are still relevant. I
need
> >> the whole team for that.
> >>
> >> Could anyone point out examples that could be removed or merged with
other
> >> examples ?
> >>
> >> Watch out , here is the list :
> >>
> >> * admin-client
> >> * authz :
> >> ** hello-world
> >> ** hello-world-authz-service
> >> ** photoz
> >> ** servlet-authz
> >> * basic-auth
> >> * saml-broker-authentication
> >> * cordova
> >> * cors :
> >> ** angular-product-app
> >> ** database-service
> >> * fuse :
> >> ** camel
> >> ** customer-app-fuse
> >> ** cxf-jaxrs
> >> ** cxf-jaxws
> >> ** external-config
> >> ** features
> >> ** fuse-admin
> >> ** product-app-fuse
> >> * js-console
> >> * kerberos
> >> * ldap
> >> * multi-tenant
> >> * saml :
> >> ** post-with-encryption
> >> ** post-with-signature
> >> ** redirect-with-signature
> >> ** servlet-filter
> >> * themes
> >> * providers :
> >> ** authenticator
> >> ** domain-extension
> >> ** event-listener-sysout
> >> ** event-store-mem
> >> ** federation-provider
> >> ** rest
> >> ** user-storage-jpa
> >> * preconfigured-demo :
> >> ** admin-access-app
> >> ** angular2-product-app
> >> ** angular-product-app
> >> ** customer-app
> >> ** customer-app-cli
> >> ** customer-app-filter
> >> ** customer-app-js
> >> ** database-service
> >> ** example-ear
> >> ** offline-access-app
> >> ** product-app
> >> ** service-account
> >> ** third-party
> >> ** third-party-cdi
> >> _______________________________________________
> >> keycloak-dev mailing list
> >> keycloak-dev(a)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
--
abstractj