Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Improve admin UI for certificate validity and signing request expiration

Aperta
  • Qualcosa non va?
#8,712 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
78/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
javascript
Ambito
frontend

Direzione di ricerca

Start with the four listed files: realDefinitions.ts, ExpiryInDaysRuleEditor.vue, RequestExpirationRuleEditor.vue, and Catalog.vue. Run the relevant Vitest tests first, then update the specified frontend titles, descriptions, labels, helper text, and empty state without changing values, policy keys, APIs, or permissions. Done means the matching tests, npm run lint, npm run stylelint, and npm run ts:check pass.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement frontend good first issue javascript

Goal

Make the admin interface clearly separate signer certificate validity from signing request expiration.

This issue changes frontend text and presentation only. Do not change policy logic, permissions, API contracts, or stored values.

Changes

Signer certificate validity

Rename:

Expiration in days

to:

Signer certificate validity

Use this field label:

Certificate validity (days)

Use a short description that explains:

  • this value is used when LibreSign creates a signer certificate;
  • it does not control how long a signing request is available.

Add helper text to explain that changing the value does not change certificates that already exist.

Do not add this setting to requester UI or personal preferences.

Signing request expiration

Rename:

Request expiration

to:

Signing request expiration

The description must say that this controls how long a signing request can remain available.

Do not change the seconds-based editor in this issue. A separate sub-issue handles duration inputs.

Access renewal

Update the frontend text for renewal_interval.

The text must not say that the signing request itself can be renewed after its maximum validity ends. It should describe renewal of signer access while the signing request is still valid.

Policy Workbench empty state

Replace this generic text:

Create a rule to delegate signature request access for specific accounts or groups.

with neutral text, for example:

Create a rule to define a different value for specific groups or accounts.

Do not add policy-specific conditions to the shared Workbench only for this text.

Main files

src/views/Settings/PolicyWorkbench/settings/expiration-rules/realDefinitions.ts
src/views/Settings/PolicyWorkbench/settings/expiration-rules/ExpiryInDaysRuleEditor.vue
src/views/Settings/PolicyWorkbench/settings/expiration-rules/RequestExpirationRuleEditor.vue
src/views/Settings/PolicyWorkbench/Catalog/Catalog.vue

Update the matching tests.

Safety

  • Do not change who can edit any policy.
  • Do not add new API requests.
  • Do not make certificate validity visible or editable in requester flows.
  • Keep all values and policy keys unchanged.

Target branch

main

Milestone: Next Major (36)

Tests

Cover the changed titles, descriptions, labels, helper text, and empty state.

Run:

  • relevant Vitest tests;
  • npm run lint;
  • npm run stylelint;
  • npm run ts:check.

Done when

  • Certificate validity is clearly named and explained.
  • Signing request expiration is clearly named and explained.
  • Access renewal text matches backend behavior.
  • The generic empty state works for all policy types.
  • No backend or permission behavior changes.
  • Tests pass.

Good first issue

The backend already has the behavior needed for this task. Keep the change limited to frontend text, labels, helper text, and tests.

Additional context
  • If you have questions, feel free to ask in this issue.
  • Give a ⭐️ star to this repository if you find LibreSign useful and would like to support the project.
  • You can also join our community: https://t.me/LibreSign
Lingua principale
PHP
Stelle
818
Fork
146
Merge medio
7h 8m
PR unite (30g)
549

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di LibreSign/libresign

Tutte le issue di LibreSign/libresign

Issue simili

Altre issue su PHP

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.