Skip to content

Commit 2f99d3c

Browse files
authored
Removed Note section
Removed Note section since this feature is GA and new API version is published
1 parent 9414d0a commit 2f99d3c

File tree

1 file changed

+0
-4
lines changed

1 file changed

+0
-4
lines changed

articles/service-fabric/how-to-managed-identity-service-fabric-app-code.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -39,10 +39,6 @@ A successful response will contain a JSON payload representing the resulting acc
3939

4040
Access tokens will be cached by Service Fabric at various levels (node, cluster, resource provider service), so a successful response does not necessarily imply that the token was issued directly in response to the user application's request. Tokens will be cached for less than their lifetime, and so an application is guaranteed to receive a valid token. It is recommended that the application code caches itself any access tokens it acquires; the caching key should include (a derivation of) the audience.
4141

42-
43-
> [!NOTE]
44-
> The only accepted API version is presently `2019-07-01-preview`, and is subject to change.
45-
4642
Sample request:
4743
```http
4844
GET 'https://localhost:2377/metadata/identity/oauth2/token?api-version=2019-07-01-preview&resource=https://vault.azure.net/' HTTP/1.1 Secret: 912e4af7-77ba-4fa5-a737-56c8e3ace132

0 commit comments

Comments
 (0)