Release under a specified FirstSpirit user
Author: king
Publication Date: 7/30/2012 13:21
Dear FirstSpirit community,
is there a way to release a FirstSpirit resource under a specified user?
Up to now, there are only the following API calls available, that will release a page under the currently connected FirstSpirit user:
de.espirit.firstspirit.access.store.IDProvider.release()
de.espirit.firstspirit.access.store.IDProvider.release(boolean)
de.espirit.firstspirit.access.store.StoreElement.release()
Maybe, there is an undocumented possibility to execute a:
release(User user)?
Might in that case really helpful, to get rid of corrupt release data very fast.
An answer is highly appreciated.
Tags: access-api, connection, documentation, release
-
Author: thmarx - 7/31/2012 9:24
Hello,
I think this is not possible. Feel free to add a feature request if you are interested in such a feature.
0 -
Author: king - 7/31/2012 10:14
Hi Thorsten,
you think it's not possible. But we need a sustainable and relyable answer. Could you clarify that in combination with FirstSpirit's core developement team?
Maybe there is an undocumented API available that might help here.
0 -
Author: feddersen - 7/31/2012 11:46
Hi Holger,
you can use a script/module that creates a new connection, using a different user to perform the release. There's no way to perform actions in the name of an user without a proper authentication.
Christoph
0 -
Author: king - 8/20/2012 19:37
Hi Christoph,
in order to do that via the non-workflow-based release call, the user needs at least project admin release permission rights. Correct?
This leads to the following steps:
[SuperAdmin connection]
- adding the user in the "Administrators" FirstSpirit group
- setting the permission right for "CAN_RELEASE" on the corresponding node
- release the changes
[plain user connection]
- re-connecting using the specified user
- releasing the store element
[SuperAdmin connection]
- undo the above changes
- release again -> using the SuperAdmin user :smileysad:
Consequence: what is won?
0 -
Author: feddersen - 8/21/2012 8:15
Hi Holger,
what do you mean with "non-workflow-based release call"?
Christoph
0 -
Author: king - 8/21/2012 10:17
I'm talking about the release-API calls:
IDProvider.release();
IDProvider.release(boolean releaseChilds);
My assumption is, that these release calls are the ones, that are provoked via "Extras" -> "Release" in JavaClient - so non-workflow-based.
0 -
Author: feddersen - 8/21/2012 10:27
The GUI provided there offers similar functionality as provided within http://www.e-spirit.com/odfs42/access/de/espirit/firstspirit/access/AccessUtil.html.
There are a couple of release methods there.
To release objects, the user needs the CAN_RELEASE permissions. He doesn't need to be project admin if that was your question. I'm still unsure what you're trying to do.
0
Please sign in to leave a comment.
Comments
7 comments