Infrastructure

I talked with ben and we believe the easiest way to take out the MyProxy portal servlet out from web.xml in the posinst script in metacat cn buildout.

In the Metacat svn trunk, the MyProxy servlet was commented out in the web.xml file. I installed the cn stacks successfully even though the two files - /etc/ssl/private/.test.dataone.org.key.pk8 and /etc/ssl/certs/.test.dataone.org.crt.publickey.

In the cn-sandbox-orc-1, I tried to reproduce the bug:
1. Moved the two files to /etc/ssl
2. Rehashed /etc/ssl/certs.
3. Rebuilt dataone-cn-metacat beta on jenkins without any change.
4. apt-get update
5. apt-get upgrade.

However, dataone-cn-metacat was upgraded successfully. And I configured metacat successfully.

So I can't reproduce the bug. Robert, did i miss anything?

In Production, the oa4mp_client.xml in Metacat contains the wrong key.

In Production, the file, oa4mp_client.xml contained the lines:

/etc/ssl/private/.test.dataone.org.key.pk8
/etc/ssl/certs/.test.dataone.org.crt.publickey

Metacat would fail to start properly until the lines were changed to

/etc/ssl/private/dataone_org.key.pk8
/etc/ssl/certs/_.dataone.org.crt.publickey

I also noticed this configuration setting in Production in the xml file:

https://mn-demo-4.test.dataone.org/metacat/ready

Ben mentioned to me that the MyProxy portal was not even needed for CN Production, so it may be useful to comment out/remove the Serlvets in the web.xml for the MyProxy portal delegation functionality in metacat during debian installation.