Skip to content

Commit 3d8c12d

Browse files
authored
Updates after reviews
1 parent 23dc373 commit 3d8c12d

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -129,10 +129,10 @@ If you have more than one plan, you can use `CredentialUtils` to get the service
129129

130130
## Visual Recognition
131131

132-
The process for authenticating with Visual Recognition has changed for service instances created after May 22, 2018. In addition, you must set the service URL.
132+
The process for authenticating with Visual Recognition has changed:
133133

134-
- For service instances created after May 22, 2018 at 4PM EDT, you authenticate to the Visual Recognition API by providing the IAM API key or access token for the service instance that you want to use. If you pass in the API key, the SDK manages the lifecycle of the credentials. You also set the correct service URL for your service by calling the `setEndPoint()` method of the service instance. See [Using IAM](#using-iam).
135-
- For service instances created before May 23, 2018, you authenticate to the Visual Recognition API by providing the API Key for the service instance that you want to use. See [API Key](#api-key)
134+
- For new service instances, authenticate by using IAM. See [Using IAM](#using-iam). Also set the service URL by calling the `setEndpoint()` method of the service instance.
135+
- For service instances created before May 23, 2018, authenticate by providing the API Key for the service instance. See [API Key](#api-key).
136136

137137
## Authentication
138138

0 commit comments

Comments
 (0)