Credential Passwords¶
Menu: Account → Credential Passwords
Use this page when you need to rotate or set SIP authentication passwords (and optional TOTP secrets) for credentials in your Sipfront account — for example after a security policy requires a password change, when Sipfront sends you a list of extensions to update without revealing the old passwords, or when you need to add new credential entries via CSV import.
What this page does¶
- Lets you update existing credential entries via CSV import (passwords, TOTP, and other entry fields) or inline password fields for small sets.
- Lets you create new credential entries (and new credential sets) via CSV import when
multi_credential_pool_idand/orentry_idare left blank — see Creating new credentials via import below. - Supports bulk updates via CSV import — the main workflow when you receive a subset of credentials from Sipfront.
- Supports CSV export (all credentials, or one large credential set) so you can edit offline and re-import.
- Offers a small inline editor for credential sets with few entries (see limits below), with a confirmation step before passwords are saved.
- Shows per-row import results (with progress) so you can see which rows succeeded or failed, and optionally export an audit CSV of those results.
Important: Current passwords are never displayed on this page. You only enter new values in the inline editor. Passwords and TOTP secrets appear only in export files.
What this page does not do¶
| Not on this page | Where instead |
|---|---|
| Rename credential sets, edit tags, or delete sets/entries in the UI | SIP Credentials in the main menu |
| Change which credentials a test uses | Projects → edit the test configuration |
| Run tests or verify registration | Projects → run tests |
| Delete credentials by omitting them from an import file | SIP Credentials — import never deletes missing rows |
Import behaviour:
| IDs in CSV | What import does |
|---|---|
Valid multi_credential_pool_id + entry_id in your account | Updates that existing entry (all entry columns in the row: username, domain, display name, auth username, password, TOTP). |
Valid multi_credential_pool_id, blank or unknown entry_id | Adds a new entry to that credential set. |
Blank or invalid multi_credential_pool_id | Creates a new credential set (and adds the entry). Rows with blank or same invalid pool id are grouped into one new set. |
| Invalid pool/entry ids | Treated like missing ids — creates a new set or entry instead of updating. |
For password rotation, use the file Sipfront sent you with pool and entry ids filled in — do not clear those columns unless you intend to create new credentials.
Credentials not listed in your import file are left unchanged (not deleted).
Best practices: export → edit → re-import¶
This is the recommended workflow when you want to bulk-manage credentials yourself (rotation, field corrections, or a focused subset of changes).
1. Export all¶
- Go to Account → Credential Passwords.
- Click Export All.
- Confirm in the dialog and download the CSV.
The file contains every credential in your account, including plaintext passwords and TOTP secrets. Treat it as confidential — store securely, transfer encrypted, delete when finished.
2. Remove unwanted lines, edit wanted lines¶
Open the CSV in Excel, LibreOffice, or a text editor.
- Remove rows you do not want to change — this keeps the import focused. Rows you delete from the file are not removed from Sipfront; they simply stay as they are. To delete credentials, use SIP Credentials in the main menu.
- Edit the rows you keep:
- Change
auth_password(andtotp_secretif needed) for rotation. - You may also correct
username,domain,display_name, orauth_usernameon update rows. - Leave
totp_secretas exported unless you intend to remove TOTP — an empty cell clears any existing TOTP on that entry. - Keep
multi_credential_pool_idandentry_idunchanged on existing rows so Sipfront updates the right records (do not clear or renumber them). - Every row you plan to import must have a non-empty
auth_password. - Do not reorder or rename CSV columns — the header must match export exactly (see CSV column reference).
- Save as CSV (UTF-8).
3. Re-import¶
- Click Import CSV.
- Choose your edited file or paste the CSV content into the text area.
- Click Import.
- Watch the Import results dialog — each row shows updated, created, or failed.
- Optionally click Export results CSV for an audit trail.
- Click OK when finished.
4. Ready to go¶
If the results look correct (expect updated for rows you edited with valid ids), your account is updated. Tests that use those credentials will load the new values on the next run.
Optionally run a small smoke test on one updated credential to confirm registration succeeds.
Recommended workflow: password rotation from a file Sipfront sent you¶
This is the typical case: you receive a CSV with your extensions/usernames without passwords, and you fill in the new passwords and upload.
1. Receive the CSV¶
Sipfront will send a CSV that includes (at minimum) these columns:
multi_credential_pool_id, entry_id, username, domain, display_name, auth_username, auth_password, totp_secret
multi_credential_pool_idandentry_ididentify the existing row in your account. Do not change or remove them.auth_passwordwill be empty (or a placeholder) — you fill in the new password for each row.totp_secret— fill in only if you are also rotating TOTP; otherwise leave empty only if the entry does not use TOTP. On update, an emptytotp_secretremoves any existing TOTP secret for that row.
You can download a format reference anytime via Sample CSV on the Credential Passwords page.
2. Fill in new passwords¶
Open the file in Excel, LibreOffice, or a text editor.
- Add the new value in the
auth_passwordcolumn for every row you need to rotate. - Keep username, domain, display_name, auth_username aligned with what Sipfront sent unless you were explicitly told to change them.
- Save as CSV (UTF-8).
Every data row must have a non-empty auth_password before import; otherwise that row will fail validation.
3. Import¶
- Go to Account → Credential Passwords.
- Click Import CSV.
- Choose your file (or paste CSV content).
- Click Import.
- Review the Import results dialog — each row shows updated, created, or failed.
- Optionally Export results CSV if you need an audit trail.
- Click OK when finished.
If all rows show updated (or the expected action), your tests that use those credentials will pick up the new passwords on the next run.
4. Verify (optional)¶
Run a small test that uses one of the updated credentials to confirm registration succeeds.
Creating new credentials via import¶
You can add credentials through Import CSV without using the SIP Credentials menu first. Leave ids blank when you want new data:
multi_credential_pool_id | entry_id | Result |
|---|---|---|
| Blank | Blank | New credential set and new entry (rows with the same blank pool id share one new set). |
| Your existing pool id | Blank | New entry in that set. |
| Your existing pool id | Existing entry id | Update that entry. |
Steps:
- Use Sample CSV on the Credential Passwords page as a template (or export an existing set and add rows with blank
entry_id). - Fill username, domain, display_name, auth_username, auth_password (and
totp_secretif needed) for each new row. - Leave
multi_credential_pool_idandentry_idempty for brand-new sets, or set onlymulti_credential_pool_idto add entries to a set you already have. - Import CSV and check the results — expect created (and “New credential set and entry created” or “New entry added to credential set”).
- Assign the new credential set to your tests in Projects (test configuration) if needed.
Notes:
- New credential sets count toward your plan limit on credential sets.
- Import does not delete or rename sets; use SIP Credentials for delete, tags, and set names after creation.
- For a single extension with a UI form, SIP Credentials → Create Credentials may still be easier than CSV.
Other ways to update passwords¶
Per-set export (large credential sets)¶
If a credential set has more than 5 entries, it appears under Bulk credential sets on this page. Inline editing is not shown for those rows.
- Open Account → Credential Passwords.
- Find the set under Bulk credential sets (paginated, 5 sets per page).
- Click Export CSV on that set.
- Edit passwords (and other fields if needed) in the file.
- Import CSV (same columns; keep
multi_credential_pool_idandentry_id).
Inline editing (small sets only)¶
For credential sets with 5 or fewer entries each, a table appears under Smaller credential sets:
- Use the column filters to find rows (
*wildcards supported; press Enter or the filter button to apply). - Type a new password in New password (leave blank to keep the current password).
- Click Save passwords, review the confirmation dialog, then confirm Update passwords.
Pagination: 10 entries per page.
Inline save updates passwords only (auth_password). Use CSV import to change TOTP or other fields.
CSV column reference¶
| Column | Required on import | Purpose |
|---|---|---|
multi_credential_pool_id | No | Internal id of the credential set. Leave blank to create a new set. Set to an existing id to add/update entries in that set. |
entry_id | No | Internal id of the entry within the set. Leave blank to create a new entry. Set with a valid pool id to update that entry. |
username | Yes | SIP username / extension |
domain | Yes | SIP domain |
display_name | Yes | Label shown in Sipfront |
auth_username | Yes | Authentication username (often same as username) |
auth_password | Yes | New SIP password |
totp_secret | No | TOTP secret (Base32), if used. On update, an empty value clears any existing TOTP. |
Header rules: The first row must be the header, with exactly these eight columns in this order. Extra columns, a different order, or data rows with the wrong column count are rejected. Download Sample CSV or use an export file as the template.
Limits: Up to 20,000 data rows per import.
FAQ¶
We received a file without passwords — is that enough?¶
Yes. Fill in auth_password (and import). Keep multi_credential_pool_id and entry_id exactly as provided so Sipfront updates the right records.
Will import change credentials we were not asked to rotate?¶
No. Only rows in your file are processed. Everything else in your account stays as it was.
If I remove rows from an export before re-importing, are those credentials deleted?¶
No. Import never deletes credentials. Removed rows are simply skipped. Delete unwanted credentials under SIP Credentials.
Can we import only part of our account?¶
Yes. A partial file is the intended rotation workflow. Match pool/entry ids for the rows you need to change.
Why don’t we see current passwords on the web page?¶
By design. Passwords are only shown in export files. The UI is for entering new values.
Import says “created” instead of “updated”¶
Usually multi_credential_pool_id or entry_id is missing, wrong, or does not belong to your account. The row was treated as a new entry (or new set). Fix the ids using the file Sipfront provided and import again. Remove any duplicate entries from SIP Credentials if a mistaken create happened.
Import failed: “missing value for auth_password”¶
Every row must include a new password. Blank auth_password cells are rejected.
Can we use this to add brand-new extensions?¶
Yes. Leave multi_credential_pool_id and entry_id blank (or only set pool id to add to an existing set). Fill in the required columns including auth_password, then Import CSV. See Creating new credentials via import. You may hit plan limits on credential sets; use SIP Credentials if you prefer the web form for one-off adds.
Does this update running tests immediately?¶
Updated passwords are stored in the database immediately. The next test run that loads those credentials uses the new values. Already-running sessions are not affected.
Is the export file secure?¶
Export All and per-set exports contain plaintext passwords and TOTP secrets. Store only on secure systems, transfer encrypted, and delete when done.
Who can access this page?¶
Users logged into your Sipfront account with access to the web UI. The page is under Account in the sidebar.
What’s the difference between this and SIP Credentials?¶
| Credential Passwords | SIP Credentials |
|---|---|
| Focus on passwords/secrets and CSV bulk import (update or create via ids) | Full CRUD on sets and entries in the UI |
| CSV import/export for bulk changes | Create, edit, delete, clone, tags |
| Does not show current passwords in the browser | Full entry editor |
| Can create entries/sets via import (blank pool/entry id) | Primary place to delete sets and manage names/tags |
| Inline editor for passwords on small sets only | Edit all fields per entry in the UI |
Quick checklist (rotation from Sipfront file)¶
- [ ] Open CSV from Sipfront; confirm
multi_credential_pool_idandentry_idare present. - [ ] Fill
auth_passwordfor every row to rotate. - [ ] Save as CSV (UTF-8); do not change column order.
- [ ] Account → Credential Passwords → Import CSV.
- [ ] Confirm import results: expect updated on each row.
- [ ] Run a smoke test on one updated credential.
Quick checklist (export → edit → re-import)¶
- [ ] Export All and store the file securely.
- [ ] Delete from the CSV only rows you do not need to touch (not deleted in Sipfront).
- [ ] Edit passwords and other fields on the rows you keep; preserve pool/entry ids.
- [ ] Import CSV and review per-row results.
- [ ] Optionally export the import results CSV for audit.
- [ ] Run a smoke test if you rotated passwords.
Support¶
If import results show unexpected created rows, failures, or pool-limit errors, contact Sipfront support with your Import results CSV export from the dialog.