Skip to content

Commit 236d38c

Browse files
committed
sentence-casing titles
1 parent 86b2288 commit 236d38c

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/azure-fluid-relay/how-tos/validate-document-creator.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,11 +10,11 @@ ms.service: azure-fluid
1010
fluid.url: https://fluidframework.com/docs/apis/azure-client/itokenprovider/
1111
---
1212

13-
# How to: Validate a User Created a Container
13+
# How to: Validate a user created a container
1414

1515
When you create a container in Azure Fluid Relay, the JWT provided by the [ITokenProvider](https://fluidframework.com/docs/apis/azure-client/itokenprovider-interface) for the creation request can only be used once. After creating a container, the client must generate a new JWT that contains the document ID (which is really the container ID) provided by the service at creation time. If an application has an authorization service that manages container access control, it will need to know who created a container with a given ID in order to authorize the generation of a new JWT for access to that container.
1616

17-
## Inform an Authorization Service when a Container is Created
17+
## Inform an authorization service when a container is created
1818

1919
An application can tie into the container creation lifecycle by implementing a public [documentPostCreateCallback()](https://fluidframework.com/docs/apis/azure-client/itokenprovider-interface#documentpostcreatecallback-methodsignature) method in its `TokenProvider`. (The name of this function can be confusing. It is really a callback for post *container* creation.) This callback will be triggered directly after creating the container, before a client requests the new JWT it needs to gain read/write permissions to the container that was created.
2020

0 commit comments

Comments
 (0)