Richard Megginson wrote:
Noriko Hosoi wrote:Richard Megginson wrote:I'm trying to make admin server install and run without having to use setup, which means I have to use hard coded values. Since directory server listens to port 389, and I don't want to have admin server listen to a low port (< 1024), how about 1389?Do you have a plan to keep retrying with some other value till it finds out an unused port? (e.g., p = 1389; p++; or p +=1000; ?)No, this would be for the port value hardcoded in to the apache config file. So it's important to pick a good default that isn't used by another well known service. I'm thinking that it would be wise to allow the user to install the rpm/pkg and specify another port e.g. rpm --define 'adminport 983'. There will also be the usual setup script/program which will allow the user to change the port post-install.
Cool! I like your proposal. How about the admin user uid? It's "admin" by default and allowed to change it (you could do it later, too). Is it needed? I'm thinking how to simplify the Admin User cache for the auth...
-------------------------------------------------------------------------- Fedora-directory-devel mailing list Fedora-directory-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-directory-devel------------------------------------------------------------------------ -- Fedora-directory-devel mailing list Fedora-directory-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-directory-devel------------------------------------------------------------------------ -- Fedora-directory-devel mailing list Fedora-directory-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-directory-devel
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
