This file is indexed.

/usr/share/arc/schema/UsernameTokenSH.xsd is in libarccommon3 4.2.0-2.

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
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema
   xmlns:ut="http://www.nordugrid.org/schemas/usernametokensh/2009/08"
   xmlns:xsd="http://www.w3.org/2001/XMLSchema"
   targetNamespace="http://www.nordugrid.org/schemas/usernametokensh/2009/08"
   elementFormDefault="qualified"
   attributeFormDefault="unqualified">

  <!-- This schema defines elements which are accepted by UsernameToken
       SecHandler. See mcc.xsd for general information about SecHandler
       elements. UsernameTokenSH plugin is expected to be used to collect 
       Security Attributes for messages comming to service and to form 
       proper Username Token SOAP Header for client outgoing messages. -->

  <xsd:element name="Process" type="ut:ProcessType"/>
  <xsd:simpleType name="ProcessType">
    <xsd:annotation>
        <xsd:documentation xml:lang="en">
          This element defines either Username Token is extracted
          from SOAP header or generated using other configuration elements.
          Type of the processing of Username Token to
          SOAP message: extract or generate.
          It is needed for both client and service side.
          Default is none.
        </xsd:documentation>
    </xsd:annotation>
    <xsd:restriction base="xsd:string">
      <xsd:enumeration value="extract"/>
      <xsd:enumeration value="generate"/>
    </xsd:restriction>
  </xsd:simpleType>

  <xsd:element name="PasswordEncoding" type="ut:PasswordEncodingType"/>
  <xsd:simpleType name="PasswordEncodingType">
    <xsd:annotation>
        <xsd:documentation xml:lang="en">
          The encoding type of the password (one part of 
          UsernameToken): text or digest.
          only needed for client side.
          Default is none.
        </xsd:documentation>
    </xsd:annotation>
    <xsd:restriction base="xsd:string">
      <xsd:enumeration value="text"/>
      <xsd:enumeration value="digest"/>
    </xsd:restriction>
  </xsd:simpleType>

  <xsd:element name="Username" type="xsd:string">
    <xsd:annotation>
        <xsd:documentation xml:lang="en">
          The Username element of the token.
          only needed for client side.
          Default is none.
        </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  
  <xsd:element name="Password" type="xsd:string">
    <xsd:annotation>
        <xsd:documentation xml:lang="en">
          The Password element of the token.
          only needed for client side.
          Default is none.
        </xsd:documentation>
    </xsd:annotation>
  </xsd:element>

  <!-- External source for password to read from. There should be a file name here. -->
  <xsd:element name="PasswordSource" type="xsd:string">
    <xsd:annotation>
        <xsd:documentation xml:lang="en">
          Location of external source for password to read from. 
          The content of the file should be like:
            user1, password1
            user2, password2
          only needed for service side.
          Default is none.
        </xsd:documentation>
    </xsd:annotation>
  </xsd:element>

</xsd:schema>