Cannot persist Active Objects without an authenticated user

Hey,
I’m working with Active Objects for the Confluence plugin I’m developing. I’ve used the Todo example: https://developer.atlassian.com/server/framework/atlassian-sdk/getting-started-with-active-objects/ as a starting point. It works fine, but then I removed all logic that force the users to be authenticated and it stopped saving my Active Objects (Todos). No error is displayed.

Is that the expected behavior for Active Objects? What if my plugin needs to persist data having no authenticated user?

There’s no reliance on having an authenticated user. Something else you deleted is breaking the plugin.

Are you accessing the AO layer on a GET request? (I’ve seen occasions where the connection pool provides a read only transaction for those).

1 Like

Same applies for a component service accessed by a REST request. Use TransactionTemplate to wrap call within a transaction

I’ve wrapped my “ao.create” code in a TransactionCallback. It worked like a charm. Thanks a lot, folks.