-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Update README and clarify userID generation #2921
Copy link
Copy link
Closed
Labels
Bot ServicesRequired for internal Azure reporting. Do not delete. Do not change color.Required for internal Azure reporting. Do not delete. Do not change color.area-docsDocumentation requiredDocumentation requiredcustomer-replied-toRequired for internal reporting. Do not delete.Required for internal reporting. Do not delete.customer-reportedRequired for internal Azure reporting. Do not delete.Required for internal Azure reporting. Do not delete.
Metadata
Metadata
Assignees
Labels
Bot ServicesRequired for internal Azure reporting. Do not delete. Do not change color.Required for internal Azure reporting. Do not delete. Do not change color.area-docsDocumentation requiredDocumentation requiredcustomer-replied-toRequired for internal reporting. Do not delete.Required for internal reporting. Do not delete.customer-reportedRequired for internal Azure reporting. Do not delete.Required for internal Azure reporting. Do not delete.
Describe the bug
I have spoken to some people who faced the same problem where there user state was shared, because they just used the example from README.md. This example already states that
userIDis an optional parameter, however it doesn't clearly state that sharing user state is a security risk. Many people useYOUR_USER_IDas a token..Example SO question
Could we possibly make this more clear?