Hi,
for auditing purposes it would be convenient to have access to the “Activity” section of a resource via API.
Best regards,
Alex
@abrix If you have Passbolt Pro is it possible to access the activity information using the action log API endpoints.
GET <PassboltURL>/actionlog/resource/<Resource_UUID>.json
GET <PassboltURL>/actionlog/folder/<Folder_UUID>.json
The API allows you to create, delete, and update your passwords. You can retrieve individual passwords as well as a list of all your passwords.
In passbolt, passwords are split into two different entities: Resources and Secrets. Passwords metadata are internally known as Resources and are represented as one object containing the name, username, the URL amongst other fields.
The actual password is part of the Secrets. It can be accessed via the Resource object association or individually. In any case the access will be logged in the system.
So, you can fetch the data from an API and it is a good idea but for security reasons, they might not enable it soon.
@abrix If you have Passbolt Pro is it possible to access the activity information using the action log API endpoints.
GET <PassboltURL>/actionlog/resource/<Resource_UUID>.json GET <PassboltURL>/actionlog/folder/<Folder_UUID>.json
I couldn’t find this API call in the documentation [1], maybe this should be included with the reference to the Passbolt Pro version.
Now it works like a charm, thank you very much.
f73eee87-e94d-4f14-a2fe-02992b0a785e Resource.Secrets.read abrix@example.com 2020-09-05T12:59:19+00:00
f76a0e60-35c1-4b85-aad0-fade6d1c5d83 Resource.Secrets.read abrix@example.com 2020-09-04T11:58:16+00:00
e2a4488d-a0cf-49ab-8471-de061976843b Resource.Secrets.read abrix@example.com 2020-09-04T11:57:55+00:00
814fcb39-1d23-4093-bfc4-e8dbba9396c9 Resources.created abrix@example.com 2020-09-04T11:57:30+00:00
The API allows you to create, delete, and update your passwords. You can retrieve individual passwords as well as a list of all your passwords.
In passbolt, passwords are split into two different entities: Resources and Secrets. Passwords metadata are internally known as Resources and are represented as one object containing the name, username, the URL amongst other fields.
The actual password is part of the Secrets. It can be accessed via the Resource object association or individually. In any case the access will be logged in the system.
So, you can fetch the data from an API and it is a good idea but for security reasons, they might not enable it soon.
Also a great feature would be a kind of administrative overview to have everything in one view e.g. if an employee leaves the company and reads all passwords which he has access to. But right now we can use the API as workaround.