Blocklet Server icon

Blocklet Server

Consume Blocklet Server API
Join our community

Actions10

Overview

This node interacts with the Blocklet Server API to manage users within a Blocklet app (team). Specifically, the "Remove User" operation deletes a user identified by their DID from a specified Blocklet app. This is useful for administrators who need to revoke access or clean up user records in their decentralized application environment.

Practical example:
An admin wants to remove a user who no longer should have access to the app. By providing the app's DID and the user's DID, this node will call the Blocklet Server API to remove that user from the team.

Properties

Name Meaning
App DID The Decentralized Identifier (DID) of the Blocklet app (team) from which to remove the user.
User DID The Decentralized Identifier (DID) of the user to be removed from the app.

Output

The output JSON contains the response from the Blocklet Server API after attempting to remove the user. Typically, this will include confirmation of the removal or details about the user deletion status. The exact structure depends on the API but generally confirms success or failure.

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential to authenticate requests to the Blocklet Server API.
  • The node uses internal helper functions to make authenticated API calls.
  • No additional external services are required beyond the Blocklet Server API.

Troubleshooting

  • Common issues:

    • Invalid or missing App DID or User DID parameters will cause the API request to fail.
    • Insufficient permissions or invalid API credentials may result in authorization errors.
    • Attempting to remove a user who does not exist in the specified app will likely return an error or empty response.

  • Error messages:

    • "Not implemented user action: removeUser" — This would indicate a misconfiguration or outdated node version; ensure the node supports the "removeUser" operation.
    • API errors returned from the Blocklet Server (e.g., 404 Not Found if user or app DID is incorrect).

  • Resolution:

    • Verify that both App DID and User DID are correct and correspond to existing entities.
    • Ensure the API key credential has sufficient permissions.
    • Check network connectivity and API endpoint availability.

Links and References

Discussion