Add comments to publishing default.xml to clarify what the elements are for.

In [3292], added comments to all the ones that I can reliably comment on. Things have changed enough through various re-workings that I do not know the purpose and usage of all the elements anymore.

Even these:

<config>
 	  <cas>
 	    <url>
 	      <base>https://${network.hosts.cas}:${network.ports.cas-ssl}/cas</base>
 	      <login>${cas.url.base}/login</login>
 	      <logout>${cas.url.base}/logout</logout>
 	      <proxy-receptor>${cas.url.base}/proxy</proxy-receptor>
 	      <proxy-validate>${cas.url.base}/proxyValidate</proxy-validate>
 	    </url>
 	  </cas>
 	
 	  <pub>
 	    <host>${network.hosts.default}:${network.ports.default}</host>
 	    <port>
 	      <http>${network.ports.default}</http>
 	      <https>${network.ports.plosone-ssl}</https>
 	    </port>
 	
 	    <url><proxy-callback>https://${network.hosts.plosone}:${network.ports.plosone-ssl}${pub.app-context}/CasProxyServlet</proxy-callback></url>

38

yes. even those. Pradeep know those better than me. And the whole CAS thing should probably just remove proxying support since we don't need it anymore.

(In [3411]) Correct the pdpName config entry for user service in the global-defaults. Remove the pdpName config overrides from other configs including the one in the packages.

Also removed the implied permissions for Fedora operations since the access service is no longer in use with Fedora.

Addresses #458

I think the following still need comments on what exactly is the use:

<cas>
 	    <url>
 	      <base>https://${network.hosts.cas}:${network.ports.cas-ssl}/cas</base>
 	      <login>${cas.url.base}/login</login>
 	      <logout>${cas.url.base}/logout</logout>
 	      <proxy-receptor>${cas.url.base}/proxy</proxy-receptor>
	      <proxy-validate>${cas.url.base}/proxyValidate</proxy-validate>
	    </url>
</cas>

According to Steve you know these better than he does.

(In [3413]) Additional docs for CAS config - Addresses #458

Thanks.

Milestone 0.8 deleted