perfsonar development work

[Michael Michalis <>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all,

FYI

This is some of the testing results for the RRD MA that may apply to all 
services. Please take special care about the LS registration issue and 
make sure that indeed your service can register with the LS. Also take 
note on the installations issues and please tell me what you think about 
the two options I have provided, or you can propose your  own.

LS Registration Testing
=================
The service failed to register to LS. After investigation it was 
concluded that the reason for this was incompatibility between the 
generated LSRegister requests of  the service and the LS implementation.


Authentication Testing
=================

*AC and UbC Profile:OK

*WE Profile: The service was unable to authenticate successfully 
requests using SAML assertions. Probable cause is that the service was 
using an older version of perfsonar-base which did not include recent 
changes in SAML assertion authentication process.


Installation Testing
==============
1)It seems there is a problem configuring the RRD MA through the web 
wizard when eXist is already installed in Tomcat and a non empty admin 
password has been set. In this case service configuration fails as the 
wizard(The ConfigurationHandler implementation to be more accurate) will 
use the empty admin password to configure exist database. This problem 
can ne solved in two ways:
a) The wizard will not initialize eXist, just set the properties in 
service.properties. In this case the wizard will not be a wizard anymore 
though
b) Add another "mock" property in wizard.properties that will ask the 
user if the wizard will use the admin password given by  the user or use 
the password stored in service.properties. Alternatively we can add 
another "mock" property called old exist admin password and the wizard 
will use that password to initialize exist rather than the one stored in 
service.properties

2)Although the service can support authentication, the necessary 
properties in components.properties and in service.properties do not 
exist. Also there is no option in setting then in the configuration 
wizard. Since authentication can be turned on and off by the value of 
one property in service.properties, I believe it would be best that the 
needed properties for authentication are included from the start in the 
properties files. The only  user input need is whether authentication 
will be turned on and if this is the case which is the URL of the AS. 
This input can be easily be retrieved through the wizard.



thanks for your attention,


Michalis Michael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHu/3boEWq51/Q/40RAu20AJ4oBJK9xmr59gJAnPqYaSGMR+Rd+gCffldU
tGGx0RvCznjLiq6DYFzuWrM=
=mw5u
-----END PGP SIGNATURE-----