Project

General

Profile

Actions
Copy link

Bug #1926

closed

CARP in 2.0 only working with username 'admin'

Added by Marcel Manz almost 14 years ago. Updated almost 14 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
CARP
Target version:
-
Start date:
10/04/2011
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.0
Affected Architecture:

Description

We upgraded from 1.2.3 where the admin user was not called admin, but eg. 'username'.

'username' was set in 2.0 in CARP settings / Remote System Username, but PfSense complained it could not synchronize to the slave. Checking the logfiles on the slave showed that the master tried to publish the configuration with 'admin' instead of the manually set 'username' user. Trying to add a user 'admin' on the slave for replication purposes only was denied with an error message that 'admin' would be a reserved username.

In order for us to make 2.0 work with CARP, we had to reset the webconfigurator admin 'username' back to 'admin'.

I assume this is a bug and should be resolved, so we can disable the default 'admin' user and use any other name.

Actions
Copy link

Also available in: Atom PDF