/usr/share/arc/schema/tls.xsd is in libarccommon1 1.1.1-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 | <?xml version="1.0" encoding="UTF-8"?>
<xsd:schema
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://www.nordugrid.org/schemas/tls/2009/08"
xmlns="http://www.nordugrid.org/schemas/tls/2009/08"
elementFormDefault="qualified"
attributeFormDefault="unqualified">
<xsd:element name="KeyPath" type="xsd:string" default="/etc/grid-security/hostkey.pem">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Location of private key.
Default is /etc/grid-security/hostkey.pem for service
and $HOME/.globus/userkey.pem for client.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="CertificatePath" type="xsd:string" default="/etc/grid-security/hostcert.pem">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Location of public certificate.
Default is /etc/grid-security/hostcert.pem for service and
$HOME/.globus/usercert.pem for client.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="ProxyPath" type="xsd:string">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Location of proxy credentials - includes certificates,
key and chain of involved certificates. Overwrites
elements KeyPath and CertificatePath. Default is /tmp/hash{userid}.0 for client,
and none for service.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="CACertificatePath" type="xsd:string">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Location of certificate of CA. Default is none.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="CACertificatesDir" default="/etc/grid-security/certificates">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Directory containing certificates of accepted CAs.
Default is /etc/grid-security/certificates
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="xsd:string">
<xsd:attribute name="PolicyGlobus" type="xsd:boolean" use="optional" default="false"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="ClientAuthn" type="xsd:boolean" default="true">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Whether checking client certificate. Only needed for service side.
Default is "true"
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="VOMSCertTrustDNChain">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
The DN list of the trusted voms server credential;
in the AC part of voms proxy certificate, voms proxy
certificate comes with the server certificate which is
used to sign the AC. So when verifying the AC on the
AC-consuming side (in ARC1, it is the MCCTLS which will
consumes the AC), the server certificate will be checked
against a trusted DN list. Only if the DN and issuer's
DN of server certificate exactly matches the DN list
in the configuration under TLS component, the AC can be trusted
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="VOMSCertTrustDN" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="VOMSCertTrustRegex" type="xsd:string" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="VOMSCertTrustDNChainsLocation" type="xsd:string">
<xsd:annotation>
<xsd:documentation xml:lang="en">
DN list in an external file, which is in the same format as VOMSCertTrustDNChain
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="VOMSProcessing" type="xsd:string">
<xsd:simpleType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
How to behave if failure happens during VOMS processing.
relaxed - use everything that passed validation.
standard - same as relaxed but fail if parsing errors took place and
VOMS extension is marked as critical. This is a default.
strict - fail if any parsing error was discovered.
noerrors - fail if any parsing or validation error happened.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="relaxed"/>
<xsd:enumeration value="standard"/>
<xsd:enumeration value="strict"/>
<xsd:enumeration value="noerrors"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="Handshake" default="TLS">
<xsd:simpleType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Type of handshake applied. Default is TLS.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="TLS"/>
<xsd:enumeration value="SSLv3"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="GSI" default="">
<xsd:simpleType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
GSI features to instest. Currently only supports Globus
without delegation.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:enumeration value=""/>
<xsd:enumeration value="globus"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:schema>
|