Here is the new documentation for all actions from websecadmin. A must for all functionalities to work is for veridiumid user to be able to restart services (sudo priviledges to details). This is the default in veridium installations - if the client changes this, most functionality will not work. Complete list of sudoers commands for veridiumid user is below
|
|
|
|
|---|---|---|
|
3.9 |
Easier configuration of CBA |
|
|
3.9 |
Elasticsearch cluster management |
|
|
3.9 |
Fido configuration |
|
|
3.9 |
All configurations should be done in websecadmin |
All templates must be modifed from now on from websecadmin and propagated to nodes. |
|
3.9 |
Custom reports generation |
|
|
3.9 |
Traceability and Logs Reporting |
|
|
3.9 |
Live change of DEBUG in log4j.xml |
|
|
3.9 |
Application CA renewal or change with a different one |
|
|
3.9 |
On fresh install there are created more journeys for different scenarious |
|
|
3.9 |
CDCR improved process - only by pointing to proper zookeeper config file |
VeridiumID Server On-Prem - Cross DataCenter Replication using the same CA (VeridiumID 3.8.4+) |
|
3.9 |
Default installation - ports are switched between shibboleth and websec. |
Now exteranal shibboleth is on 443 (no certificate) and websec on 8944 (client certificate) |
|
3.9 |
Renewal of OPA certificate |
Renewal is done from websecadmin and automatically propagated to nodes - Renew internal application certificates |
|
3.9 |
Better visibility on certificate expiration dates |
Display new certificates in dashboard Also for AD and Default certs - to review the certificate documentation ; also include renewal in admin and ssp IDP certs. |
|
3.9.1 |
Freeradius clients configuration and json logs |
|
|
3.9.1 |
Renew Persistence Veridium CA and change of Certificates (veridium or client) for persistence layer. |
Renew Veridium persistance CA and replace certificate exposed by persistance services |
|
3.9.1 |
Export logs for sessions/devices and identity. |
/etc/sudoers.d/veridiumid-user
veridiumid ALL=(root) NOPASSWD: /bin/systemctl stop ver_*
veridiumid ALL=(root) NOPASSWD: /bin/systemctl start ver_*
veridiumid ALL=(root) NOPASSWD: /bin/systemctl enable ver_*
veridiumid ALL=(root) NOPASSWD: /bin/systemctl disable ver_*
veridiumid ALL=(root) NOPASSWD: /bin/systemctl restart ver_*
veridiumid ALL=(root) NOPASSWD: /bin/systemctl status ver_*
To restrict access to infrastructure-related operations and custom reporting, a new admin-limited role has been introduced. The role grants all administrative permissions except INFRA and CUSTOMREPORTS, enabling day-to-day platform administration while keeping critical infrastructure and reporting capabilities restricted.