I think it isn't documented because we only use it for testing and don't believe it's recommended*. Generally, I go and delete everything the user has touched before I delete a user. Otherwise, you can't delete the user because it created something or was assigned permission to something.
Here's an example with curl:
curl -X DELETE
http://localhost:8080/api/admin/authenticatedUsers/jdoeI hope this helps. I wouldn't recommend doing it through the database.
* Here's what the Javadoc says at
https://github.com/IQSS/dataverse/blob/v4.2.1/src/main/java/edu/harvard/iq/dataverse/authorization/AuthenticationServiceBean.java#L203Use with care! This method was written primarily for developers interested in API testing who want to:
1. Create a temporary user and get an API token.
2. Do some work with that API token.
3. Delete all the stuff that was created with the API token.
4. Delete the temporary user.
Before calling this method, make sure you've deleted all the stuff tied to the user, including stuff they've created, role assignments, group assignments, etc. Longer term, the intention is to have a "disableAuthenticatedUser" method/command.