Whitelisting and auditing of ApplicationIntegrationToolset #3823
Replies: 1 comment
-
|
Response from ADK Answering Agent (experimental, answer may be inaccurate) TLDR: You can configure whitelisting at the toolset level and handle user-specific permissions via OAuth2. Auditing is best done through logging, and you can use Application Integration workflows directly in addition to Hi @maheshwaritanay, Thanks for your questions. Here are some pointers on how to achieve what you're looking for with the Whitelisting Entities and ActionsYou can control which entities and actions are exposed by the toolset during its initialization. The For user-level permissions, the recommended approach is to use an authentication scheme like OAuth 2.0. [4] When a user authenticates, the AuditingFor auditing, the best practice is to implement robust logging within your agent. You should create logs for all actions performed by the toolset, attributing each action to the user who initiated it. This ensures you have a clear audit trail. You can find more on this in the ADK documentation on safety and security best practices. [3] Application Integration UI DocumentationWhen you refer to the "application integration UI", it could mean a couple of things:
Using Integrations Beyond
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi team,
we are using ApplicationIntegrationToolset to connect with enterprise tools like JIRA, confluence, tables. We want to be able to whitelist the entities and actions at user level. I tried searching for the examples but couldnt find. Is there any provision to do this?
Also need help for relevant documentation to use application integration UI. How these integrations can be used in google ADK other than default ExecuteConnection.
Beta Was this translation helpful? Give feedback.
All reactions