I am currently in the process of converting several automation workflows from SOMA to the REST Management Interface. I’ve encountered an issue where certain asynchronous calls to the actionqueue leave management sessions open , which is causing downstream failures in my workflow.
The Scenario:
- I trigger a domain backup via a POST to
/mgmt/actionqueue/{domain}.
- I receive the expected
200 OK response with the "pending" action status.
- Once the backup is complete, I successfully download the file.
- However, the session remains active. When I view the ActiveUsers status resource (
/mgmt/status/default/ActiveUsers), the user and session ID are still listed as logged in.
The Conflict:
Later in the same workflow, I attempt to delete the domain to reset the environment. This operation fails with an error stating the domain cannot be deleted because a user is currently logged in.
We did not experience this with SOMA, as those request/response cycles seemed to terminate the session context immediately. With the REST interface, synchronous calls (like GET config) don't seem to have this problem, but asynchronous actionqueue operations appear to keep the session "pinned."
My Questions:
- Is there an RMI endpoint specifically for invalidating a session or logging out a user?
- Has anyone found a way to programmatically clear active users via the REST API?
- Are there specific headers or configurations for the
rest-mgmt service that force a session to close once the initial "pending" response is delivered?
Any insights or workarounds from the community would be greatly appreciated.