5.3. Decision Server token-based authentication
You can also use token-based authentication for communication between Red Hat Decision Manager and Decision Server. You can use the complete token as a system property of your application server, instead of the user name and password, for your applications. However, you must ensure that the token will not expire while the applications are interacting because the token is not automatically refreshed. To get the token, see 「Token-based authentication」.
Procedure
To configure Business Central to manage Decision Server using tokens:
-
Set the
org.kie.server.tokenproperty. Make sure that the
org.kie.server.userandorg.kie.server.pwdproperties are not set.Red Hat Decision Manager will then use the
Authorization: Bearer $TOKENauthentication method.
-
Set the
To use the REST API using the token-based authentication:
-
Set the
org.kie.server.controller.tokenproperty. -
Make sure that the
org.kie.server.controller.userandorg.kie.server.controller.pwdproperties are not set.
-
Set the
Because Decision Server is unable to refresh the token, use a high-lifespan token. A token’s lifespan must not exceed January 19 2038. Check with your security best practices to see whether this is a suitable solution for your environment.