Hello Paras,
As you mentioned "standalone mode" I immediately thought in the keycloak
server [1]. However having a look at your link I've realized that you must
be trying to secure your application. That json file is the adapter config
(keycloak.json) that by default is in the WEB-INF folder of your war
application.
Hope it helps,
Luis
[1]
El jue., 14 mar. 2019 a las 16:00, Paras Jain (<pjain(a)rivetlogic.com>)
escribió:
Thanks for your responses Luis and Bruno. I have started looking at
quickstart in more details yesterday and they are helpful. Just to give a
little more background to my specific problem. We are using Keycloak for
last 2-3 months. We are running it successfully in standalone mode. Right
now we are facing a CORS issue and to resolve that CORS issue I need to
place updated keycloak.json somewhere, but I don't know where. I have
downloaded the file from admin console as mentioned in
https://www.keycloak.org/docs/2.5/securing_apps/topics/oidc/java/java-ada...
and made necessary modifications. I don't know how to apply it. That is my
immediate challenge.
------------------------------
Paras Jain
rivetlogic <
http://www.rivetlogic.com/>
Voice +1.703.879.3097
Skype paras.jain_rivetlogic
GTalk pjain(a)rivetlogic.com
Calendar paras jain's calendar
<
http://www.google.com/calendar/hosted/rivetlogic.com/embed?src=pjain%40ri...
On Thu, Mar 14, 2019 at 6:38 AM Luis Rodríguez Fernández <
uo67113(a)gmail.com> wrote:
> Hello Paras,
>
> Yes, definitely quickstarts and latest documentation are good places to
> start.
>
> There is also a keycloak docker image [1]. Just creating the admin user
> and
> adding your json should be enough for you:
> docker run -e KEYCLOAK_USER=<USERNAME> -e KEYCLOAK_PASSWORD<PASSWORD> \
> -e KEYCLOAK_IMPORT=/tmp/example-realm.json -v
> /tmp/example-realm.json:/tmp/example-realm.json jboss/keycloak
>
> As well you can run it from sources using maven [2]:
>
> mvn -f keycloak/testsuite/utils/pom.xml exec:java -Pkeycloak-server
> -Dimport=/tmp/example-realm.json
>
> Hope it helps,
>
> Luis
>
> [1]
https://hub.docker.com/r/jboss/keycloak/
> [2]
>
>
https://db-blog.web.cern.ch/blog/luis-rodriguez-fernandez/2018-12-testing...
>
>
> El mié., 13 mar. 2019 a las 20:16, Bruno Oliveira (<bruno(a)abstractj.org>)
> escribió:
>
> > Hi Paras, I'd suggest to look at the quickstarts. They may provide some
> > guidance
https://github.com/keycloak/keycloak-quickstarts.
> >
> > Also, the latest docs are here:
> >
https://www.keycloak.org/documentation.html
> >
> >
> > On 2019-03-13, Paras Jain wrote:
> > > Hi,
> > >
> > > I am running keycloak in standalone mode. As per
> > >
> >
>
https://www.keycloak.org/docs/2.5/securing_apps/topics/oidc/java/java-ada...
> > > I have copied the client config from admin console and created a
> > > keycloak.json. But I don't know where to put this file for it to take
> > > effect. Is there any documentation for that?
> > >
> > > --
> > > CONFIDENTIALITY NOTICE: This e-mail, including attachments, is for the
> > sole
> > > use of the intended recipient(s) and may contain confidential and
> > > privileged information or otherwise be protected by law. Any
> > unauthorized
> > > review, use, disclosure or distribution is prohibited. If you are not
> > the
> > > intended recipient, please contact the sender and destroy all copies
> and
> > > the original message.
> > > _______________________________________________
> > > keycloak-user mailing list
> > > keycloak-user(a)lists.jboss.org
> > >
https://lists.jboss.org/mailman/listinfo/keycloak-user
> >
> > --
> >
> > abstractj
> > _______________________________________________
> > keycloak-user mailing list
> > keycloak-user(a)lists.jboss.org
> >
https://lists.jboss.org/mailman/listinfo/keycloak-user
> >
>
>
> --
>
> "Ever tried. Ever failed. No matter. Try Again. Fail again. Fail better."
>
> - Samuel Beckett
> _______________________________________________
> keycloak-user mailing list
> keycloak-user(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/keycloak-user
CONFIDENTIALITY NOTICE: This e-mail, including attachments, is for the sole use of the
intended recipient(s) and may contain confidential and privileged information or otherwise
be protected by law. Any unauthorized review, use, disclosure or distribution is
prohibited. If you are not the intended recipient, please contact the sender and destroy
all copies and the original message.
--
"Ever tried. Ever failed. No matter. Try Again. Fail again. Fail better."
- Samuel Beckett