We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/1nbuc/mcp-integration-suite'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
involved-roles-3968091.md•1.17 kB
<!-- loio3968091c619048729d789686dd7a74cd -->
# Involved Roles
The security artifact renewal process requires that different persons perform a sequence of steps in a coordinated way on each side of the communication. The exact sequence depends on the kind of security material which is renewed and on the use case.
**Roles in the Security Artifact Renewal Process**
<table>
<tr>
<th valign="top">
Role
</th>
<th valign="top">
Tasks
</th>
</tr>
<tr>
<td valign="top">
Sender/receiver administrator \(at customer side\)
</td>
<td valign="top">
Updates the security artifacts owned by the sender/receiver back-end system \(for example, the keystore\).
</td>
</tr>
<tr>
<td valign="top">
Integration developer
</td>
<td valign="top">
Updates the integration flow in certain use cases.
</td>
</tr>
<tr>
<td valign="top">
Tenant administrator
</td>
<td valign="top">
Updates the security artifacts of the tenant \(relevant for outbound communication\).
</td>
</tr>
<tr>
<td valign="top">
Load balancer administrator
</td>
<td valign="top">
Updates the security artifacts of the load balancer \(relevant for inbound communication\).
</td>
</tr>
</table>