AA Conf call 12 November2007

From GEANT2-JRA1 Wiki

12th of November 10:00 CET.

  • We will use the Hungarnet MCU,
    • GDS numbering plan JRA1: 0036100309901
    • Phone access: +36 1 450 3099 then type the GDS number 0036100309901

Agenda

  • Actions reviews
  • JavaWebStart problem for perfsonarUI (and CNM), dependency on eduGAIN

Actions

  • CNM
    1. NJ, AH to try out psUI with java 1.6 and send results to the mailing list.
    2. CR to reproduce the problem using java 1.4 and 1.6. Then send results to the mailing list.
    3. CR to send a stripped down version of the jar
    4. DS and PM to test with the stripped down jar version and send results to the mailing list on Wednesday along with the envisaged next steps.
    5. DS and PM to describe scenarios of utilisation of the certificates and where they are stored. Those scenarios will be sent to JRA5 for security evaluation.(for 15/12, final answer from JRa5 expected 12/12)
  • perfsonarUI
    1. CR and NJ to look into the perfsonar base code to identify the cause of the error identified by Nina (email 12/11).
    2. NJ and CR to describe scenarios of utilisation of the certificates and where they are stored. Those scenarios will be sent to JRA5 for security evaluation (for 15/12, final answer from JRa5 expected 12/12).
  • SSH/Telnet MP
    1. SM to send the URL of an instance of the SSH/Telnet MP for testing (Tuesday). - Done
  • VisualperfSONAR
    1. CR to work with DM to describe scenarios of utilisation of the certificates and where they are stored. Those scenarios will be sent to JRA5 for security evaluation. (for 15/12, final answer from JRa5 expected 12/12)
  • CR to send the pointer to the error code for the authentication part (AS and authentication on web-services to the developers)
  • CR to push for clearer SASL CA exceptions.
  • Visualisation developers to identify if the error code messages are sufficient to capture a misbehavior of the service or why a request was rejected.
  • CR to send the list of error code to Erlangen for consistency.

Minutes

Attendance: Candido, David, Patricia, Nina, Stijn M, Stijn V, Andreas, Nicolas

  • CNM Update:
    • Issue when using hava 1.4 or 1.6.
  • pSUI Update
    • Series of issues solved last week with the help of JRA5 and of the mailing list.
    • Succesful access of the SASL CA server. Errors observed with java 1.6.
    • Following steps: integrate Auth for other services (tabs)
    • Question: should the authentication be separated for each tab. Answer: no. This is easier for the user and psUI is considered as one tool.
    • CR: the certificates are valid 8 hours.
    • How to store the certificates? In memory or in file? Answer: In memory.
  • SSH/Telnet MP:
    • a working version will be deployed tomorrow. The URL will be sent to the mailing list. - Done
  • MDM service: no authentication for the SSH/Telnet MP. Authentication expected easrly 2008.
  • This was about SASL CA client, which is a piece of code written by somebody else, and throwing same "null pointer" exception, regardless

the type of error. Thus, one can't distinguish whether the SASL CA is not responding at all, or there is something wrong with user/password or anything else. Since SASL CA client is already at SVN, I thought we could modify it a little bit to throw more reasonable exceptions, and therefore provide more detailed feedback to the user.

  • CR to add exceptions following Nina's request.
  • Error codes: specifeid on the error code page
Personal tools