Request history¶
The Request history module logs the ACM requests that were processed: who asked for which alias, from which agent and for which application, and what was answered. An administrator uses it to audit vault accesses, understand a refusal, or extract a period.
ACM availability
The ACM screen and its five modules only appear in the console when ACM is allowed: both a licence covering ACM and the Allow ACM usage option enabled for your tenant are required.
Request list¶
The grid only has two columns, the first one gathering the whole context of the request.
| Column | Content |
|---|---|
| Information | Four to five icon-prefixed lines: the request date in the console time zone, the identifier used, the issuing ACM agent, the calling application, then the alias requested. A missing value does not display its line. |
| Request status | In bold, the exact outcome; in italics below it, the family it belongs to. |
A coloured vertical bar at the start of the row recalls the family: blue for a success, red for a failure, orange for a refusal.
Possible outcomes¶
| Family | Outcomes |
|---|---|
| Success | Success — the password was delivered. |
| Request failed | Server Error, Vault error, Invalid parameters. |
| Request denied | Unknown alias, No contract, No application, Request denied — this last case means a contract was found but its restrictions were not met. |
As long as no request has been recorded, the grid shows No request.
Filter the list¶
A Filters panel, collapsed by default, sits above the grid. It offers three exclusive modes, selected by radio button, plus an independent date filter.
| Mode | Description |
|---|---|
| All (default) | No filter on the content. |
| Request status | A checkbox group over three columns, one per family: Success, Request failed, Request denied. No box ticked is equivalent to all of them. |
| Keyword | Substring searched in the identifier, the requested alias, the application and the agent — not in the date. |
| Field | Description |
|---|---|
| Date | Checkbox enabling the period filter. |
| Starting date | As dd/mm/yyyy. Cannot go beyond today. |
| Ending date | As dd/mm/yyyy. Pulled back to the start date when it precedes it, and capped at today. The stated day is included. |
Sections select themselves
There is no need to click the radio button before typing: ticking a status box or entering a keyword selects the matching mode and resets the others. Likewise, changing a date ticks the Date box. An abandoned mode therefore loses its input.
Click Display to apply the filters and collapse the panel, or Reset to clear them. Once a filter is active, the panel title becomes Current filter followed by the retained criterion and, where applicable, the period.
Export¶
The Export all pages button downloads an acm_requests.csv file, semicolon-separated,
holding the requests matching the current filters — not merely the displayed page.
The file opens with a context header: an Organization line and its name, the period bounds when the date filter is active, then an Exportation date line. After two blank lines come the six columns:
| Column | Content |
|---|---|
| Date | Request date, in ISO 8601 format. ⚠ Unlike the grid, the export does not bring it back into the console time zone. |
| ACM login | Identifier used by the request. |
| ACM agent | Issuing agent. |
| Alias requested | Alias targeted in the vault. |
| ACM application | Calling executable. |
| Request status | Outcome, under its label — never as a code. |