I would strongly suggest you reconsider and use the Keycloak login as there
are many many reasons why that is a better approach. I'm not going to list
it again, because I've done that to many times to count. The login page is
highly customizable so you can make it look exactly how you like. Any
specific reasons why this is not an option?
If you still insist on doing it the "wrong way" then use the OAuth2
resource owner credential grant instead, take a look at
https://keycloak.gitbooks.io/securing-client-applications-guide/content/t...
for more details.
On 2 February 2017 at 00:00, akash agrawal <akash_agrawal(a)yahoo.co.uk>
wrote:
Hi,
I am evaluating Keycloak for our Identity management needs. We have a
collection of REST APIs which we want to secure using OAuth/OpenIdConnect.
I am looking over Keycloak documentation to determine if a client
application can call a REST endpoint (production grade) to get the access
token. Are there other alternatives to get access token? Using KeyCloak
user interface to login and get an access token is not an option.
Appreciate your help. Thanks.
Akash
_______________________________________________
keycloak-user mailing list
keycloak-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user