I posted about that when I discovered it a year ago. It seems silly to have a field that is ignored and something else used instead. Is that still in 2.3 that way? It seems like it would be easy to change that from a field to the word "admin."
-- Steve Yates ITS, Inc. -----Original Message----- From: List [mailto:[email protected]] On Behalf Of Olivier Mascia Sent: Sunday, April 24, 2016 6:05 PM To: pfSense Support and Discussion Mailing List <[email protected]> Subject: Re: [pfSense] XMLRPC sync - user/password limitations? And a possible bug regarding 'admin' user > Le 25 avr. 2016 à 00:34, Olivier Mascia <[email protected]> a écrit : > > /xmlrpc.php: webConfigurator authentication error for 'admin' from 172.16.0.2 > during sync settings. > > The user setup on the primary firewall is not 'admin'. So if the secondary > attempts to validate the password against 'admin', that could be the issue. Just re-read once again the Book. OK, I read too fast on those two lines: " Set Remote System Username to admin. Note: This must always be admin, no other user will work! " Took them for default example values, while the small comment says this is not an exercise. Why is there a box to enter the remote system username, when it is useless and has to be 'admin' anyway?... :) What privilege limitations can be made to user 'admin', and still get it to work for xmlrpc? I don't like keeping a user named admin, no matter how strong the password might be, so I usually disable it and create a new one with all the required rights for full administration. -- Meilleures salutations, Met vriendelijke groeten, Best Regards, Olivier Mascia, integral.be/om _______________________________________________ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold _______________________________________________ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
