Upgrading a machine to use the proxy.
To convert an older build where the PKI system wasn't proxied: awk '{print $0} /Define an AJP 1.3 Connector on port/ {print "<Connector port=\"9447\" protocol=\"AJP/1.3\" redirectPort=\"9444\" />}" }' /etc/pki-ca/server.xml > server.xml.new ; mv server.xml.new /etc/pki-ca/server.xml sed -e "s/\[PKI_MACHINE_NAME\]/$HOSTNAME/g" -e "s/\[PKI_AJP_PORT\]/9444/g" /usr/share/pki/ca/conf/proxy.conf > /etc/pki-ca/proxy.conf I've used the default ports here. Adjest is you've altered yours. IPA copies the proxy.conf file into /etc/httpd/conf.d and renames it. You can do the same thing by hand. I'm not sure if this should go into PKI or IPA.
Adam Young wrote:
To convert an older build where the PKI system wasn't proxied:
awk '{print $0} /Define an AJP 1.3 Connector on port/ {print "<Connector port=\"9447\" protocol=\"AJP/1.3\" redirectPort=\"9444\" />}" }' /etc/pki-ca/server.xml > server.xml.new ; mv server.xml.new /etc/pki-ca/server.xml
sed -e "s/\[PKI_MACHINE_NAME\]/$HOSTNAME/g" -e "s/\[PKI_AJP_PORT\]/9444/g" /usr/share/pki/ca/conf/proxy.conf > /etc/pki-ca/proxy.conf
I've used the default ports here. Adjest is you've altered yours.
IPA copies the proxy.conf file into /etc/httpd/conf.d and renames it. You can do the same thing by hand.
I'm not sure if this should go into PKI or IPA.
Since these are dogtag configuration files I think dogtag needs to handle updating them. rob
OK, here's something closer to releasable and written in Perl. This script will upgrade the proxy ports to 9444 by default, or allow you to override by setting the first parameter.
Thanks Adam! FWIW I was kinda hoping for new development we would start using Python and have as a general goal of migrating Perl code to Python as opportunities arose. Python is the company preferred scripting language. Once upon a time I was a Perl fan boy, I though it was the greatest thing since sliced bread, after all it was light years better than writing shell scripts. Then I got introduced to Python and I never looked back, Python is a much better language, much easier to write clean structured maintainable code in. Just my 2 cents, just a thought. /me John puts his flame resistant Nomex suit on and prepares to get flamed in the programming language war :-) -- John Dennis <jdennis@redhat.com> Looking to carve out IT costs? www.redhat.com/carveoutcosts/
On 09/16/2011 08:58 AM, John Dennis wrote:
Thanks Adam!
FWIW I was kinda hoping for new development we would start using Python and have as a general goal of migrating Perl code to Python as opportunities arose.
Python is the company preferred scripting language. Once upon a time I was a Perl fan boy, I though it was the greatest thing since sliced bread, after all it was light years better than writing shell scripts. Then I got introduced to Python and I never looked back, Python is a much better language, much easier to write clean structured maintainable code in. Just my 2 cents, just a thought.
/me John puts his flame resistant Nomex suit on and prepares to get flamed in the programming language war :-)
OK already has too many languages involved. I'm no weilling to sff sny motr. We are working on a plan to simplify a lot of the stuff that wwe currently do in Perl, but it too will unlikely be in Python. Since this project is priamily Java, And the pkisilet program is the start point for doing a/utomated cofiguration, it will likely be in pkisilent written in Java./
On 09/16/2011 08:09 AM, Adam Young wrote:
On 09/16/2011 08:58 AM, John Dennis wrote:
Thanks Adam!
FWIW I was kinda hoping for new development we would start using Python and have as a general goal of migrating Perl code to Python as opportunities arose.
Python is the company preferred scripting language. Once upon a time I was a Perl fan boy, I though it was the greatest thing since sliced bread, after all it was light years better than writing shell scripts. Then I got introduced to Python and I never looked back, Python is a much better language, much easier to write clean structured maintainable code in. Just my 2 cents, just a thought.
/me John puts his flame resistant Nomex suit on and prepares to get flamed in the programming language war :-)
OK already has too many languages involved. I'm no weilling to sff sny motr.
We are working on a plan to simplify a lot of the stuff that wwe currently do in Perl, but it too will unlikely be in Python. Since this project is priamily Java, And the pkisilet program is the start point for doing a/utomated cofiguration, it will likely be in pkisilent written in Java./ jython
_______________________________________________ Freeipa-devel mailing list Freeipa-devel@redhat.com https://www.redhat.com/mailman/listinfo/freeipa-devel
On 09/16/2011 10:09 AM, Adam Young wrote:
We are working on a plan to simplify a lot of the stuff that wwe currently do in Perl, but it too will unlikely be in Python. Since this project is priamily Java, And the pkisilet program is the start point for doing a/utomated cofiguration, it will likely be in pkisilent written in Java./
I'm cool with that, Java is a decent language. Perl is just plain evil. -- John Dennis <jdennis@redhat.com> Looking to carve out IT costs? www.redhat.com/carveoutcosts/
participants (4)
-
Adam Young -
John Dennis -
Rich Megginson -
Rob Crittenden