Hi, > 2.5) A method of synchronizing configuration files (apart from certain > variables) across multiple servers. If all Radiator servers have very similar > configuration and are distributed for load balancing and redundancy, it's a > shame that the configuration needs to be managed and configured separately > for each server. There are differences between servers, but the bulk of the > configuration can remain the same. > > There is 3rd party software such as rsync for synchronizing files, but the > variables for each Radiator configuration file have to be within the file > itself (as far as I can tell). If the variables could be configured outside > of each configuration file, such as a header file, this would allow for > synchronizing the configuration files effectively across all servers while > still taking into account the differences between each server.
eh??? we do multi server configuration syncing already - you know that you can just include different files for each server...using...a headerfile as you say - our radius.cfg contains all local requirements and then pulls in the local config file for the server. (in our case we use a database to hold all details, generate the required new configs for each server then push out to each server) > 2.6) A more secure method for storing credentials, at the moment they can > only be stored locally on the Radiator servers. Perhaps integration with > popular 3rd party solutions (such as CyberArk) if their API permits it. read discussions on the list - if stored elsewhere there are still security issues. what are you hoping to fix/resolve? you can store configs on a remote DB if there are basic local issues (though anyone with admin access could still read the DB credentials and then connect to the DB to get hold of config). alan _______________________________________________ radiator mailing list radiator@open.com.au http://www.open.com.au/mailman/listinfo/radiator
