Adding Larksuite detectors to support their token base and API key/secret based credentials. Here are some more details about Larksuite supported credentials:
App Id and Secret: They belongs to custom application created on Larksuite development portal. These credentials will be used to obtain access tokens:
Access Tokens: Larksuite supports 3 different type of tokens:
Tenant Token: The app executes corresponding operations on behalf of the tenant (i.e., the enterprise or team) Prefix: t-xxxxxxxxxxxxx
App Token: The app executes corresponding operations using its own identity, not associated with a specific enterprise or user, such as obtaining the identity of the currently login user. Prefix: a-xxxxxxxxxxxxx
User Token: The app executes corresponding operations on behalf of the user, such as creating a cloud document or a calendar event through the API. Prefix: u-xxxxxxxxxxxxx
Note: Due to the limited usage scenarios of app_access_token, the Lark Open Platform is gradually unifying app_access_token and tenant_access_token.
Checklist:
[ ] Tests passing (make test-community)?
[x] Lint passing (make lint this requires golangci-lint)?
Description:
Adding Larksuite detectors to support their token base and API key/secret based credentials. Here are some more details about Larksuite supported credentials:
Prefix: t-xxxxxxxxxxxxxPrefix: a-xxxxxxxxxxxxxPrefix: u-xxxxxxxxxxxxxNote: Due to the limited usage scenarios of app_access_token, the Lark Open Platform is gradually unifying app_access_token and tenant_access_token.
Checklist:
make test-community)?make lintthis requires golangci-lint)?