BlissRadius: configuration, profiles, and customer accounts

Role of the integration

BlissRadius remains the technical authentication and accounting platform, while ISP Billing connects each remote account with its customer, installation address, commercial service, profile, and lifecycle state. Do not configure a second Radius provider for the same access unless a controlled migration defines ownership and rollback.

API and database setup

Configure the BlissRadius server address and dedicated API username and password, then verify the generated URL. Configure database host, port, database name, username, and password separately and run the dedicated SQL test.

API and database are different dependencies: a successful database connection does not prove that remote account actions work. Use least privilege, TLS, VPN or filtered private connectivity, and never publish the database. Some installations may hide these settings because they are managed centrally.

Profiles and the default option

A profile defines its internal name, default option, Radius attributes, and the description shown to customers. Attributes may represent sessions without DNS, with DNS, or with DNS and DHCP pool, together with the supported parental-control rules.

Use only operators and attributes supported by BlissRadius. Explain the actual network effect and inspect linked accounts, services, and child options before editing or deleting a profile.

Additional options and parental control

Options extend a profile with a different set of Radius attributes and a separate commercial description. Customer Area may allow the account holder to request an option change, but ISP Billing requires OTP delivery and confirmation before applying it.

Use a reliable recipient and describe DNS policy, limits, expected reconnection, and how filtering can be disabled. Parental-control DNS is a policy tool, not an absolute security guarantee.

Create an account

Select the correct customer and installation address, then enter username, password, optional static IP, profile, state, and account type: PPPoE, VPN, or Internal use. Internal notes must not contain reusable secrets.

Available states are Active, Suspended, and Terminated. After saving, verify the remote account, authentication, assigned address, profile, and session. Send credentials only through an authorized recipient and secure template.

Service, state, and disconnect

The service link connects technical access with commercial billing. Account detail exposes the linked profile, state, and PPPoE data. Disconnect ends the current session so the device must authenticate again; it does not suspend or terminate the account.

The Unbilled services view identifies technical access without a valid economic association. Correct customer and service linkage instead of deleting the remote resource or concealing the mismatch.

Requests, sessions, and diagnosis

Access requests show Radius authentication attempts and their outcomes. Session history reports start, stop, mode, traffic, addresses, and termination causes when available; internal help relates common causes to settings such as Idle-Timeout.

Diagnose in order: service state, account state, profile and option, credentials, Radius request, session, address assignment, API, and database. Limit access and retention because logs and exports can identify customers and usage patterns.

Customer Area

The customer widget exposes only the permitted account state and PPPoE information. Where enabled, it can offer a profile-option change protected by OTP and disconnect the active session so that the new attributes are applied at the next authentication.

Verify account-holder identity, OTP recipient, technical consequences, and any price impact before enabling self-service. Never expose passwords, management addresses, internal attributes, or another customer’s data.

Checklist

• Choose one Radius authority per access
• Test API and database separately
• Use dedicated credentials and filtered networking
• Create profiles with supported attributes
• Explain every customer option
• Protect option changes with OTP
• Link the correct customer and address
• Select PPPoE, VPN, or Internal deliberately
• Distinguish disconnect from suspension
• Reconcile unbilled services
• Inspect requests and sessions in order
• Limit customer-visible and exported data