| 17 | | * Client looks for proxy according to following rules: |
| 18 | | {{{ |
| 19 | | #!div style="font-size: 90%" |
| 20 | | {{{#!default |
| 21 | | It first checks the X509_USER_PROXY system property. If the property |
| 22 | | is not set, it checks next the 'proxy' property in the current |
| 23 | | configuration. If that property is not set, then it defaults to a |
| 24 | | value based on the following rules: |
| 25 | | If a UID system property is set, and running on a Unix machine it |
| 26 | | returns /tmp/x509up_u${UID}. If any other machine then Unix, it returns |
| 27 | | ${tempdir}/x509up_u${UID}, where tempdir is a platform-specific |
| 28 | | temporary directory as indicated by the java.io.tmpdir system property. |
| 29 | | If a UID system property is not set, the username will be used instead |
| 30 | | of the UID. That is, it returns ${tempdir}/x509up_u_${username} |
| 31 | | }}} |
| 32 | | }}} |
| | 16 | Dostęp do infrastruktury QCG możliwy jest z dowolnego komputera na którym zainstalowany jest klient QCG-Broker. |
| | 17 | Dla wygody użytkowników uruchomiona została maszyna dostępowa (qcg.man.poznan.pl) z zainstalowaną wersją klienta dla użytkowników PL-GRID. |
| 34 | | * Client looks for the CA directory according to following rules: |
| 35 | | {{{ |
| 36 | | #!div style="font-size: 90%" |
| 37 | | {{{#!sh |
| 38 | | It first checks the X509_CERT_DIR system property. If the property |
| 39 | | is not set, it checks next the 'cacert' property in the current |
| 40 | | configuration. If that property is not set, it tries to find |
| 41 | | the certificates using the following rules: |
| 42 | | First the ${user.home}/.globus/certificates directory is checked. |
| 43 | | If the directory does not exist, and on a Unix machine, the |
| 44 | | /etc/grid-security/certificates directory is checked next. |
| 45 | | If that directory does not exist and GLOBUS_LOCATION |
| 46 | | system property is set then the ${GLOBUS_LOCATION}/share/certificates |
| 47 | | directory is checked. |
| 48 | | }}} |
| 49 | | }}} |
| | 19 | Logowanie: ssh <plguser>@qcg.man.poznan.pl |
| | 20 | np. ssh plgpiontek@qcg.man.poznan.pl |
| 51 | | CoG library configuration can be modified using the COG properties file `~/.globus/cog.properties` |
| 52 | | {{{ |
| 53 | | #!div style="font-size: 90%" |
| 54 | | {{{#!sh |
| 55 | | #Java CoG Kit Configuration File |
| 56 | | proxy=/tmp/x509up_u501 |
| 57 | | cacert=/etc/grid-security/certificates/ |
| 58 | | }}} |
| 59 | | }}} |
| 60 | | |
| 61 | | Additionaly the location of user's certificate and private key must be specified. |
| 62 | | {{{ |
| 63 | | #!div style="font-size: 90%" |
| 64 | | {{{#!sh |
| 65 | | usercert=/home/piontek/.globus/usercert.pem |
| 66 | | userkey=/home/piontek/.globus/userkey.pem |
| 67 | | }}} |
| 68 | | }}} |
| 69 | | If they are specified and user proxy certificate doesn't exist it will be automatically created by the client. Otherwise the proxy certificate has to be created by `grid-proxy-init` tool. |
| 70 | | |
| | 22 | Przy logowaniu należy podać hasło ustawione w portalu PL-GRID. |
