From 5f2d79181158c3dc83adbdf7f866264d04cb8490 Mon Sep 17 00:00:00 2001 From: Lars Hvam Date: Wed, 9 Oct 2019 05:15:57 +0200 Subject: [PATCH] another one --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 451c26a..3609882 100644 --- a/README.md +++ b/README.md @@ -170,7 +170,7 @@ Service credentials and other parameters that must be specified at Watson servic Identity and Access Management (IAM) is a bearer-token based authentication method. Token management is either performed by the ABAP SDK or must be implemented by the SDK user.
If username / password or apikey are provided for method `zcl_ibmc_service_ext=>get_instance()`, the ABAP SDK under the cover generates a bearer-token when needed and refreshes it when it is about to expire.
If neither username / password nor apikey are provided for method `zcl_ibmc_service_ext=>get_instance()`, the ABAP SDK user must implement an individual token management. Before a service method is called the first time, a valid bearer-token must be provided to the Watson service wrapper ABAP class instance as follows: -``` +```abap lo_service_class->set_bearer_token( i_bearer_token = '...' ). ``` Afterwards, service methods can be called as long as the provided token is valid. When the token has expired, the method above must be called again with a new (refreshed) bearer-token as parameter.