glassfish 0.1.1-universal-java-1.5

Sign up to get free protection for your applications and to get access to all the features.
Files changed (135) hide show
  1. data/COPYRIGHT +33 -0
  2. data/LICENSE.txt +263 -0
  3. data/README +12 -0
  4. data/bin/asadmin +7 -0
  5. data/bin/asadmin.bat +8 -0
  6. data/bin/glassfish_rails +40 -0
  7. data/config/asadminenv.conf +6 -0
  8. data/config/asenv.bat +28 -0
  9. data/config/asenv.conf +27 -0
  10. data/config/glassfish.container +4 -0
  11. data/domains/domain1/config/admin-keyfile +3 -0
  12. data/domains/domain1/config/cacerts.jks +0 -0
  13. data/domains/domain1/config/default-web.xml +906 -0
  14. data/domains/domain1/config/domain-passwords +0 -0
  15. data/domains/domain1/config/domain.xml +208 -0
  16. data/domains/domain1/config/keyfile +6 -0
  17. data/domains/domain1/config/keystore.jks +0 -0
  18. data/domains/domain1/config/logging.properties +82 -0
  19. data/domains/domain1/config/login.conf +18 -0
  20. data/domains/domain1/config/server.policy +160 -0
  21. data/domains/domain1/config/sun-acc.xml +40 -0
  22. data/domains/domain1/config/wss-server-config-1.0.xml +86 -0
  23. data/domains/domain1/config/wss-server-config-2.0.xml +94 -0
  24. data/domains/domain1/docroot/favicon.gif +0 -0
  25. data/domains/domain1/docroot/index.html +87 -0
  26. data/domains/domain1/master-password +0 -0
  27. data/lib/appclient/appclientlogin.conf +10 -0
  28. data/lib/appclient/client.policy +79 -0
  29. data/lib/appclient/wss-client-config-1.0.xml +84 -0
  30. data/lib/appclient/wss-client-config-2.0.xml +96 -0
  31. data/lib/dtds/application-client_1_2.dtd +292 -0
  32. data/lib/dtds/application-client_1_3.dtd +506 -0
  33. data/lib/dtds/application_1_2.dtd +197 -0
  34. data/lib/dtds/application_1_3.dtd +312 -0
  35. data/lib/dtds/connector_1_0.dtd +561 -0
  36. data/lib/dtds/ejb-jar_1_1.dtd +894 -0
  37. data/lib/dtds/ejb-jar_2_0.dtd +1671 -0
  38. data/lib/dtds/sun-application-client-container_1_0.dtd +123 -0
  39. data/lib/dtds/sun-application-client-container_1_1.dtd +264 -0
  40. data/lib/dtds/sun-application-client-container_1_2.dtd +267 -0
  41. data/lib/dtds/sun-application-client_1_3-0.dtd +57 -0
  42. data/lib/dtds/sun-application-client_1_4-0.dtd +182 -0
  43. data/lib/dtds/sun-application-client_1_4-1.dtd +431 -0
  44. data/lib/dtds/sun-application-client_5_0-0.dtd +495 -0
  45. data/lib/dtds/sun-application_1_3-0.dtd +30 -0
  46. data/lib/dtds/sun-application_1_4-0.dtd +44 -0
  47. data/lib/dtds/sun-application_5_0-0.dtd +51 -0
  48. data/lib/dtds/sun-cmp-mapping_1_0.dtd +100 -0
  49. data/lib/dtds/sun-cmp-mapping_1_1.dtd +99 -0
  50. data/lib/dtds/sun-cmp-mapping_1_2.dtd +106 -0
  51. data/lib/dtds/sun-connector_1_0-0.dtd +66 -0
  52. data/lib/dtds/sun-connector_1_5-0.dtd +62 -0
  53. data/lib/dtds/sun-domain_1_0.dtd +2007 -0
  54. data/lib/dtds/sun-domain_1_1.dtd +3080 -0
  55. data/lib/dtds/sun-domain_1_2.dtd +3697 -0
  56. data/lib/dtds/sun-domain_1_3.dtd +3867 -0
  57. data/lib/dtds/sun-ejb-jar_2_0-0.dtd +449 -0
  58. data/lib/dtds/sun-ejb-jar_2_0-1.dtd +454 -0
  59. data/lib/dtds/sun-ejb-jar_2_1-0.dtd +756 -0
  60. data/lib/dtds/sun-ejb-jar_2_1-1.dtd +1085 -0
  61. data/lib/dtds/sun-ejb-jar_3_0-0.dtd +1113 -0
  62. data/lib/dtds/sun-loadbalancer_1_0.dtd +156 -0
  63. data/lib/dtds/sun-loadbalancer_1_1.dtd +172 -0
  64. data/lib/dtds/sun-resources_1_0.dtd +650 -0
  65. data/lib/dtds/sun-resources_1_1.dtd +650 -0
  66. data/lib/dtds/sun-resources_1_2.dtd +662 -0
  67. data/lib/dtds/sun-resources_1_3.dtd +732 -0
  68. data/lib/dtds/sun-server_1_0.dtd +1056 -0
  69. data/lib/dtds/sun-web-app_2_3-0.dtd +230 -0
  70. data/lib/dtds/sun-web-app_2_3-1.dtd +230 -0
  71. data/lib/dtds/sun-web-app_2_4-0.dtd +466 -0
  72. data/lib/dtds/sun-web-app_2_4-1.dtd +742 -0
  73. data/lib/dtds/sun-web-app_2_5-0.dtd +789 -0
  74. data/lib/dtds/web-app_2_2.dtd +639 -0
  75. data/lib/dtds/web-app_2_3.dtd +1063 -0
  76. data/lib/dtds/web-jsptaglibrary_1_1.dtd +265 -0
  77. data/lib/dtds/web-jsptaglibrary_1_2.dtd +468 -0
  78. data/lib/package-appclient.xml +185 -0
  79. data/lib/processLauncher.properties +25 -0
  80. data/lib/processLauncher.xml +189 -0
  81. data/lib/schemas/XMLSchema.dtd +402 -0
  82. data/lib/schemas/application-client_1_4.xsd +267 -0
  83. data/lib/schemas/application-client_5.xsd +304 -0
  84. data/lib/schemas/application_1_4.xsd +315 -0
  85. data/lib/schemas/application_5.xsd +336 -0
  86. data/lib/schemas/connector_1_5.xsd +1036 -0
  87. data/lib/schemas/datatypes.dtd +203 -0
  88. data/lib/schemas/ejb-jar_2_1.xsd +2208 -0
  89. data/lib/schemas/ejb-jar_3_0.xsd +2706 -0
  90. data/lib/schemas/j2ee_1_4.xsd +1608 -0
  91. data/lib/schemas/j2ee_jaxrpc_mapping_1_1.xsd +886 -0
  92. data/lib/schemas/j2ee_web_services_1_1.xsd +491 -0
  93. data/lib/schemas/j2ee_web_services_client_1_1.xsd +345 -0
  94. data/lib/schemas/javaee_5.xsd +2096 -0
  95. data/lib/schemas/javaee_web_services_1_2.xsd +747 -0
  96. data/lib/schemas/javaee_web_services_client_1_2.xsd +578 -0
  97. data/lib/schemas/jax-rpc-ri-config.xsd +416 -0
  98. data/lib/schemas/jsp_2_0.xsd +308 -0
  99. data/lib/schemas/jsp_2_1.xsd +343 -0
  100. data/lib/schemas/orm_1_0.xsd +1516 -0
  101. data/lib/schemas/persistence_1_0.xsd +260 -0
  102. data/lib/schemas/web-app_2_4.xsd +1234 -0
  103. data/lib/schemas/web-app_2_5.xsd +1271 -0
  104. data/lib/schemas/web-jsptaglibrary_2_0.xsd +1010 -0
  105. data/lib/schemas/web-jsptaglibrary_2_1.xsd +1144 -0
  106. data/lib/schemas/xml.xsd +82 -0
  107. data/modules/admin-cli-10.0-SNAPSHOT.jar +0 -0
  108. data/modules/auto-depends-0.2-SNAPSHOT.jar +0 -0
  109. data/modules/cli-framework-10.0-SNAPSHOT.jar +0 -0
  110. data/modules/common-ee-util-10.0-SNAPSHOT.jar +0 -0
  111. data/modules/common-util-10.0-SNAPSHOT.jar +0 -0
  112. data/modules/config-0.2-SNAPSHOT.jar +0 -0
  113. data/modules/config-api-10.0-SNAPSHOT.jar +0 -0
  114. data/modules/gf-jruby-connector-10.0-SNAPSHOT.jar +0 -0
  115. data/modules/glassfish-10.0-SNAPSHOT.jar +0 -0
  116. data/modules/glassfish-api-10.0-SNAPSHOT.jar +0 -0
  117. data/modules/glassfish.rb +10 -0
  118. data/modules/grizzly-framework-1.7.1.jar +0 -0
  119. data/modules/grizzly-http-1.7.1.jar +0 -0
  120. data/modules/grizzly-http-utils-1.7.1.jar +0 -0
  121. data/modules/grizzly-jruby-1.7.0.jar +0 -0
  122. data/modules/grizzly-jruby-module-1.7.0.jar +0 -0
  123. data/modules/grizzly-module-1.7.1.jar +0 -0
  124. data/modules/grizzly-portunif-1.7.1.jar +0 -0
  125. data/modules/grizzly-rcm-1.7.1.jar +0 -0
  126. data/modules/hk2-0.2-SNAPSHOT.jar +0 -0
  127. data/modules/hk2-core-0.2-SNAPSHOT.jar +0 -0
  128. data/modules/junit-4.3.1.jar +0 -0
  129. data/modules/kernel-10.0-SNAPSHOT.jar +0 -0
  130. data/modules/persistence-api-1.0b.jar +0 -0
  131. data/modules/servlet-api-2.5.jar +0 -0
  132. data/modules/sjsxp-1.0.jar +0 -0
  133. data/modules/stax-api-1.0-2.jar +0 -0
  134. data/modules/tiger-types-1.0.jar +0 -0
  135. metadata +206 -0
@@ -0,0 +1,123 @@
1
+
2
+ <!ENTITY % boolean "(yes | no | on | off | 1 | 0 | true | false)">
3
+ <!ENTITY % severity "(FINEST|FINER|FINE|CONFIG|INFO|WARNING|SEVERE|ALERT|FATAL)">
4
+
5
+ <!-- iAS Application client container configuration
6
+ send-password Specifies whether client authentication credentials should
7
+ be sent to the server. Without credential all accesses to
8
+ protected EJBs will result in exceptions.
9
+ -->
10
+ <!ELEMENT client-container (target-server, auth-realm?, client-credential?, log-service?, property*)>
11
+ <!ATTLIST client-container send-password %boolean; "true">
12
+
13
+ <!-- Target server's IIOP listener configuration
14
+ name Application server instance name
15
+ address ip address or hostname (resolvable by DNS) of the ORB
16
+ port port number of the ORB
17
+ -->
18
+ <!ELEMENT target-server (description?, security?)>
19
+ <!ATTLIST target-server name CDATA #REQUIRED
20
+ address CDATA #REQUIRED
21
+ port CDATA #REQUIRED>
22
+
23
+ <!ELEMENT description (#PCDATA)>
24
+
25
+ <!-- Default client credentials that will be sent to server. If this element
26
+ is present, then it will be automatically sent to the server, without
27
+ prompting the user for usename and password on the client side.
28
+ user-name User name credential
29
+ password Password credential
30
+ realm The realm (specified by name) where credentials are to be
31
+ resolved.
32
+ -->
33
+ <!ELEMENT client-credential (property*)>
34
+ <!ATTLIST client-credential user-name CDATA #REQUIRED
35
+ password CDATA #REQUIRED
36
+ realm CDATA #IMPLIED>
37
+
38
+ <!-- Logging service configuration.
39
+
40
+ file By default log file will be at $APPCLIENT_ROOT/logs/client.log
41
+ Can use this attribute to specify an alternate location.
42
+ level sets the base level of severity. Messages at or above this
43
+ setting get logged into the log file.
44
+ -->
45
+ <!ELEMENT log-service (property*)>
46
+ <!ATTLIST log-service file CDATA #IMPLIED
47
+ level %severity; "SEVERE">
48
+
49
+ <!-- SSL security configuration for IIOP/SSL communication with
50
+ the target-server.
51
+ -->
52
+ <!ELEMENT security (ssl, cert-db)>
53
+
54
+ <!-- Define SSL processing parameters
55
+
56
+ cert-nickname nickname of the server certificate in the certificate database
57
+ or the PKCS#11 token. In the certificate, the name format is
58
+ tokenname:nickname. Including the tokenname: part of the name
59
+ in this attribute is optional.
60
+
61
+ ssl2-enabled (optional) Determines whether SSL2 is enabled.
62
+
63
+ ssl3-enabled (optional) Determines whether SSL3 is enabled.
64
+
65
+ If both SSL2 and SSL3 are enabled for a virtual server, the server
66
+ tries SSL3 encryption first. If that fails, the server tries SSL2
67
+ encryption.
68
+
69
+ ssl2ciphers (optional) A space-separated list of the SSL2 ciphers used, with
70
+ the prefix + to enable or - to disable, for example +rc4. Allowed
71
+ values are rc4, rc4export, rc2, rc2export, idea, des, desede3.
72
+
73
+ ssl3-tls-ciphers (optional) A space-separated list of the SSL3 ciphers used, with
74
+ the prefix + to enable or - to disable, for example +rsa_des_sha.
75
+ Allowed SSL3 values are rsa_rc4_128_md5, rsa3des_sha, rsa_des_sha,
76
+ rsa_rc4_40_md5, rsa_rc2_40_md5, rsa_null_md5. Allowed TLS values
77
+ are rsa_des_56_sha, rsa_rc4_56_sha.
78
+
79
+ tls-enabled (optional) Determines whether TLS is enabled.
80
+
81
+ tls-rollback-enabled (optional) Determines whether TLS rollback is enabled. TLS
82
+ rollback should be enabled for Microsoft Internet Explorer
83
+ 5.0 and 5.5.
84
+
85
+ client-auth-enabled (optional) Determines whether SSL3 client authentication is
86
+ performed on every request, independent of ACL-based access
87
+ control.
88
+ -->
89
+ <!ELEMENT ssl EMPTY>
90
+ <!ATTLIST ssl cert-nickname CDATA #IMPLIED
91
+ ssl2-enabled CDATA "false"
92
+ ssl2-ciphers CDATA #IMPLIED
93
+ ssl3-enabled CDATA "true"
94
+ ssl3-tls-ciphers CDATA #IMPLIED
95
+ tls-enabled CDATA "true"
96
+ tls-rollback-enabled CDATA "true">
97
+
98
+ <!-- Location and password to read the Certificate Database. iAS
99
+ (actually NSS) will provide utilities with which a certificate
100
+ database can be created.
101
+
102
+ path Specifies the absolute path where the cert database (cert7.db)
103
+ is stored.
104
+ password needed to open and read a cert database
105
+ -->
106
+ <!ELEMENT cert-db EMPTY>
107
+ <!ATTLIST cert-db path CDATA #REQUIRED
108
+ password CDATA #REQUIRED>
109
+
110
+ <!-- JAAS is available on Application Client Container.
111
+ Optional configuration for JAAS authentication realm.
112
+
113
+ name defines the name of this realm
114
+ classname defines the java class which implements this realm
115
+ -->
116
+ <!ELEMENT auth-realm (property*)>
117
+ <!ATTLIST auth-realm name CDATA #REQUIRED
118
+ classname CDATA #REQUIRED>
119
+
120
+ <!-- Syntax for supplying properties as name value pairs -->
121
+ <!ELEMENT property EMPTY>
122
+ <!ATTLIST property name CDATA #REQUIRED
123
+ value CDATA #REQUIRED>
@@ -0,0 +1,264 @@
1
+
2
+ <!ENTITY % boolean "(yes | no | on | off | 1 | 0 | true | false)">
3
+ <!ENTITY % severity "(FINEST|FINER|FINE|CONFIG|INFO|WARNING|SEVERE|ALERT|FATAL)">
4
+
5
+ <!-- iAS Application client container configuration
6
+ send-password Specifies whether client authentication credentials should
7
+ be sent to the server. Without credential all accesses to
8
+ protected EJBs will result in exceptions.
9
+ message-security-config: Optional list of layer specific lists of
10
+ configured message security providers.
11
+ -->
12
+ <!ELEMENT client-container (target-server, auth-realm?, client-credential?, log-service?, message-security-config*, property*)>
13
+ <!ATTLIST client-container send-password %boolean; "true">
14
+
15
+ <!-- Target server's IIOP listener configuration
16
+ name Application server instance name
17
+ address ip address or hostname (resolvable by DNS) of the ORB
18
+ port port number of the ORB
19
+ -->
20
+ <!ELEMENT target-server (description?, security?)>
21
+ <!ATTLIST target-server name CDATA #REQUIRED
22
+ address CDATA #REQUIRED
23
+ port CDATA #REQUIRED>
24
+
25
+ <!ELEMENT description (#PCDATA)>
26
+
27
+ <!-- Default client credentials that will be sent to server. If this element
28
+ is present, then it will be automatically sent to the server, without
29
+ prompting the user for usename and password on the client side.
30
+ user-name User name credential
31
+ password Password credential
32
+ realm The realm (specified by name) where credentials are to be
33
+ resolved.
34
+ -->
35
+ <!ELEMENT client-credential (property*)>
36
+ <!ATTLIST client-credential user-name CDATA #REQUIRED
37
+ password CDATA #REQUIRED
38
+ realm CDATA #IMPLIED>
39
+
40
+ <!-- Logging service configuration.
41
+
42
+ file By default log file will be at $APPCLIENT_ROOT/logs/client.log
43
+ Can use this attribute to specify an alternate location.
44
+ level sets the base level of severity. Messages at or above this
45
+ setting get logged into the log file.
46
+ -->
47
+ <!ELEMENT log-service (property*)>
48
+ <!ATTLIST log-service file CDATA #IMPLIED
49
+ level %severity; "SEVERE">
50
+
51
+ <!-- SSL security configuration for IIOP/SSL communication with
52
+ the target-server.
53
+ -->
54
+ <!ELEMENT security (ssl, cert-db)>
55
+
56
+ <!-- Define SSL processing parameters
57
+
58
+ cert-nickname nickname of the server certificate in the certificate database
59
+ or the PKCS#11 token. In the certificate, the name format is
60
+ tokenname:nickname. Including the tokenname: part of the name
61
+ in this attribute is optional.
62
+
63
+ ssl2-enabled (optional) Determines whether SSL2 is enabled.
64
+
65
+ ssl3-enabled (optional) Determines whether SSL3 is enabled.
66
+
67
+ If both SSL2 and SSL3 are enabled for a virtual server, the server
68
+ tries SSL3 encryption first. If that fails, the server tries SSL2
69
+ encryption.
70
+
71
+ ssl2ciphers (optional) A space-separated list of the SSL2 ciphers used, with
72
+ the prefix + to enable or - to disable, for example +rc4. Allowed
73
+ values are rc4, rc4export, rc2, rc2export, idea, des, desede3.
74
+
75
+ ssl3-tls-ciphers (optional) A space-separated list of the SSL3 ciphers used, with
76
+ the prefix + to enable or - to disable, for example +rsa_des_sha.
77
+ Allowed SSL3 values are rsa_rc4_128_md5, rsa3des_sha, rsa_des_sha,
78
+ rsa_rc4_40_md5, rsa_rc2_40_md5, rsa_null_md5. Allowed TLS values
79
+ are rsa_des_56_sha, rsa_rc4_56_sha.
80
+
81
+ tls-enabled (optional) Determines whether TLS is enabled.
82
+
83
+ tls-rollback-enabled (optional) Determines whether TLS rollback is enabled. TLS
84
+ rollback should be enabled for Microsoft Internet Explorer
85
+ 5.0 and 5.5.
86
+
87
+ client-auth-enabled (optional) Determines whether SSL3 client authentication is
88
+ performed on every request, independent of ACL-based access
89
+ control.
90
+ -->
91
+ <!ELEMENT ssl EMPTY>
92
+ <!ATTLIST ssl cert-nickname CDATA #IMPLIED
93
+ ssl2-enabled CDATA "false"
94
+ ssl2-ciphers CDATA #IMPLIED
95
+ ssl3-enabled CDATA "true"
96
+ ssl3-tls-ciphers CDATA #IMPLIED
97
+ tls-enabled CDATA "true"
98
+ tls-rollback-enabled CDATA "true">
99
+
100
+ <!-- Location and password to read the Certificate Database. iAS
101
+ (actually NSS) will provide utilities with which a certificate
102
+ database can be created.
103
+
104
+ path Specifies the absolute path where the cert database (cert7.db)
105
+ is stored.
106
+ password needed to open and read a cert database
107
+ -->
108
+ <!ELEMENT cert-db EMPTY>
109
+ <!ATTLIST cert-db path CDATA #REQUIRED
110
+ password CDATA #REQUIRED>
111
+
112
+ <!-- JAAS is available on Application Client Container.
113
+ Optional configuration for JAAS authentication realm.
114
+
115
+ name defines the name of this realm
116
+ classname defines the java class which implements this realm
117
+ -->
118
+ <!ELEMENT auth-realm (property*)>
119
+ <!ATTLIST auth-realm name CDATA #REQUIRED
120
+ classname CDATA #REQUIRED>
121
+
122
+ <!-- Syntax for supplying properties as name value pairs -->
123
+ <!ELEMENT property EMPTY>
124
+ <!ATTLIST property name CDATA #REQUIRED
125
+ value CDATA #REQUIRED>
126
+
127
+ <!--
128
+ The message-layer entity is used to define the value of the
129
+ auth-layer attribute of message-security-config elements.
130
+
131
+ Used in: message-security-config
132
+ -->
133
+ <!ENTITY % message-layer "(SOAP)">
134
+
135
+ <!--
136
+ The message-security-config element defines the message layer
137
+ specific provider configurations of the application server.
138
+
139
+ All of the providers within a message-security-config element
140
+ must be able to perform authentication processing at
141
+ the message layer defined by the value of the auth-layer
142
+ attribute.
143
+
144
+ The default-provider attribute may be used to identify
145
+ the server provider to be invoked for any application
146
+ for which a specific server provider has not been bound.
147
+
148
+ The default-client-provider attribute may be used to identify
149
+ the client provider to be invoked for any application
150
+ for which a specific client provider has not been bound.
151
+
152
+ At most one (non-null) default server provider and at most one
153
+ (non-null) default client provider may be identified
154
+ among all the same layer message-security-config elements.
155
+
156
+ When a default provider of a type is not defined for a message
157
+ layer, the container will only invoke a provider of the type
158
+ (at the layer) for those applications for which a specific
159
+ provider has been bound.
160
+
161
+ Default:
162
+ Used in: security-service
163
+ -->
164
+ <!ELEMENT message-security-config ( provider-config+ )>
165
+ <!ATTLIST message-security-config
166
+ auth-layer %message-layer; #REQUIRED
167
+ default-provider CDATA #IMPLIED
168
+ default-client-provider CDATA #IMPLIED>
169
+
170
+ <!--
171
+ The provider-config element defines the configuration of
172
+ an authentication provider.
173
+
174
+ The provider-id attibute contains an identifier that can be used to
175
+ reference the provider-config.
176
+
177
+ The request-policy and response-policy sub-elements define
178
+ the authentication policy requirements associated
179
+ with the request and response processing performed by the
180
+ authentication provider (respectively).
181
+
182
+ the provider-type attribute defines whether the provider is a client
183
+ authentication provider or a server authentication provider.
184
+
185
+ The class-name attribute defines the java implementation class of the
186
+ provider. Client authentication providers must implement the
187
+ com.sun.enterprise.security.jauth.ClientAuthModule interface. Server-side
188
+ providers must implement the com.sun.enterprise.security.jauth.ServerAuthModule
189
+ interface. A provider may implement both interfaces, but it must implement
190
+ the interface corresponding to its provider type.
191
+
192
+ The optional list of property elements may be used to configure provider
193
+ specific property values. These values will be passed to the provider
194
+ when its initialize method is called.
195
+
196
+ A provider-config with no contained request-policy or response-policy
197
+ sub-elements, is a null provider. The container will not instantiate
198
+ or invoke the methods of a null provider, and as such the implementation
199
+ class of a null provider need not exist.
200
+
201
+ Default:
202
+ Used in: message-security-config
203
+ -->
204
+ <!ELEMENT provider-config ( request-policy?, response-policy?, property* )>
205
+ <!ATTLIST provider-config
206
+ provider-id CDATA #REQUIRED
207
+ provider-type (client | server | client-server) #REQUIRED
208
+ class-name CDATA #REQUIRED>
209
+
210
+ <!--
211
+ The request-policy element is used to define the authentication policy
212
+ requirements associated with the request processing performed by an
213
+ authentication provider (i.e. when a client provider's
214
+ ClientAuthModule.initiateRequest method is called or when a
215
+ server provider's ServerAuthModule.validateRequest is called).
216
+
217
+ The auth-source attribute defines a requirement for message layer
218
+ sender authentication (e.g. username password) or content authentication
219
+ (e.g. digital signature).
220
+
221
+ The auth-recipient attribute defines a requirement for message
222
+ layer authentication of the reciever of a message to its sender (e.g. by
223
+ XML encryption).
224
+
225
+ The before-content attribute value indicates that recipient
226
+ authentication (e.g. encryption) is to occur before any
227
+ content authentication (e.g. encrypt then sign) with respect
228
+ to the target of the containing auth-policy.
229
+
230
+ Default:
231
+ Used in: provider-config
232
+ -->
233
+ <!ELEMENT request-policy EMPTY >
234
+ <!ATTLIST request-policy
235
+ auth-source (sender | content) #IMPLIED
236
+ auth-recipient (before-content | after-content) #IMPLIED>
237
+ <!--
238
+ The response-policy element is used to define the authentication policy
239
+ requirements associated with the response processing performed by an
240
+ authentication provider (i.e. when a client provider's
241
+ ClientAuthModule.validateResponse method is called or when a
242
+ server provider's ServerAuthModule.secureResponse method is called).
243
+
244
+ The auth-source attribute defines a requirement for message layer
245
+ sender authentication (e.g. username password) or content authentication
246
+ (e.g. digital signature).
247
+
248
+ The auth-recipient attribute defines a requirement for message
249
+ layer authentication of the reciever of a message to its sender (e.g. by
250
+ XML encryption).
251
+
252
+ The before-content attribute value indicates that recipient
253
+ authentication (e.g. encryption) is to occur before any
254
+ content authentication (e.g. encrypt then sign) with respect
255
+ to the target of the containing auth-policy.
256
+
257
+ Default:
258
+ Used in: provider-config
259
+ -->
260
+ <!ELEMENT response-policy EMPTY >
261
+ <!ATTLIST response-policy
262
+ auth-source (sender | content) #IMPLIED
263
+ auth-recipient (before-content | after-content) #IMPLIED>
264
+
@@ -0,0 +1,267 @@
1
+
2
+ <!ENTITY % boolean "(yes | no | on | off | 1 | 0 | true | false)">
3
+ <!ENTITY % severity "(FINEST|FINER|FINE|CONFIG|INFO|WARNING|SEVERE|ALERT|FATAL)">
4
+
5
+ <!-- iAS Application client container configuration
6
+ send-password Specifies whether client authentication credentials should
7
+ be sent to the server. Without credential all accesses to
8
+ protected EJBs will result in exceptions.
9
+ message-security-config: Optional list of layer specific lists of
10
+ configured message security providers.
11
+ -->
12
+ <!ELEMENT client-container (target-server+, auth-realm?, client-credential?, log-service?, message-security-config*, property*)>
13
+ <!ATTLIST client-container send-password %boolean; "true">
14
+
15
+ <!-- Target server's IIOP listener configuration
16
+ name Application server instance name
17
+ address ip address or hostname (resolvable by DNS) of the ORB
18
+ port port number of the ORB
19
+ -->
20
+ <!ELEMENT target-server (description?, security?)>
21
+ <!ATTLIST target-server name CDATA #REQUIRED
22
+ address CDATA #REQUIRED
23
+ port CDATA #REQUIRED>
24
+
25
+ <!ELEMENT description (#PCDATA)>
26
+
27
+ <!-- Default client credentials that will be sent to server. If this element
28
+ is present, then it will be automatically sent to the server, without
29
+ prompting the user for usename and password on the client side.
30
+ user-name User name credential
31
+ password Password credential
32
+ realm The realm (specified by name) where credentials are to be
33
+ resolved.
34
+ -->
35
+ <!ELEMENT client-credential (property*)>
36
+ <!ATTLIST client-credential user-name CDATA #REQUIRED
37
+ password CDATA #REQUIRED
38
+ realm CDATA #IMPLIED>
39
+
40
+ <!-- Logging service configuration.
41
+
42
+ file By default log file will be at $APPCLIENT_ROOT/logs/client.log
43
+ Can use this attribute to specify an alternate location.
44
+ level sets the base level of severity. Messages at or above this
45
+ setting get logged into the log file.
46
+ -->
47
+ <!ELEMENT log-service (property*)>
48
+ <!ATTLIST log-service file CDATA #IMPLIED
49
+ level %severity; "SEVERE">
50
+
51
+ <!-- SSL security configuration for IIOP/SSL communication with
52
+ the target-server.
53
+ -->
54
+ <!ELEMENT security (ssl, cert-db)>
55
+
56
+ <!-- Define SSL processing parameters
57
+
58
+ cert-nickname nickname of the server certificate in the certificate database
59
+ or the PKCS#11 token. In the certificate, the name format is
60
+ tokenname:nickname. Including the tokenname: part of the name
61
+ in this attribute is optional.
62
+
63
+ ssl2-enabled (optional) Determines whether SSL2 is enabled.
64
+
65
+ ssl3-enabled (optional) Determines whether SSL3 is enabled.
66
+
67
+ If both SSL2 and SSL3 are enabled for a virtual server, the server
68
+ tries SSL3 encryption first. If that fails, the server tries SSL2
69
+ encryption.
70
+
71
+ ssl2ciphers (optional) A space-separated list of the SSL2 ciphers used, with
72
+ the prefix + to enable or - to disable, for example +rc4. Allowed
73
+ values are rc4, rc4export, rc2, rc2export, idea, des, desede3.
74
+
75
+ ssl3-tls-ciphers (optional) A space-separated list of the SSL3 ciphers used, with
76
+ the prefix + to enable or - to disable, for example
77
+ +SSL_RSA_WITH_RC4_128_MD5.
78
+ Allowed SSL3/TLS values are SSL_RSA_WITH_RC4_128_MD5,
79
+ SSL_RSA_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_DES_CBC_SHA,
80
+ SSL_RSA_EXPORT_WITH_RC4_40_MD5, SSL_RSA_WITH_NULL_MD5,
81
+ SSL_RSA_WITH_RC4_128_SHA,SSL_RSA_WITH_NULL_SHA
82
+
83
+
84
+ tls-enabled (optional) Determines whether TLS is enabled.
85
+
86
+ tls-rollback-enabled (optional) Determines whether TLS rollback is enabled. TLS
87
+ rollback should be enabled for Microsoft Internet Explorer
88
+ 5.0 and 5.5.
89
+
90
+ client-auth-enabled (optional) Determines whether SSL3 client authentication is
91
+ performed on every request, independent of ACL-based access
92
+ control.
93
+ -->
94
+ <!ELEMENT ssl EMPTY>
95
+ <!ATTLIST ssl cert-nickname CDATA #IMPLIED
96
+ ssl2-enabled CDATA "false"
97
+ ssl2-ciphers CDATA #IMPLIED
98
+ ssl3-enabled CDATA "true"
99
+ ssl3-tls-ciphers CDATA #IMPLIED
100
+ tls-enabled CDATA "true"
101
+ tls-rollback-enabled CDATA "true">
102
+
103
+ <!-- Location and password to read the Certificate Database. iAS
104
+ (actually NSS) will provide utilities with which a certificate
105
+ database can be created.
106
+
107
+ path Specifies the absolute path where the cert database (cert7.db)
108
+ is stored.
109
+ password needed to open and read a cert database
110
+ -->
111
+ <!ELEMENT cert-db EMPTY>
112
+ <!ATTLIST cert-db path CDATA #REQUIRED
113
+ password CDATA #REQUIRED>
114
+
115
+ <!-- JAAS is available on Application Client Container.
116
+ Optional configuration for JAAS authentication realm.
117
+
118
+ name defines the name of this realm
119
+ classname defines the java class which implements this realm
120
+ -->
121
+ <!ELEMENT auth-realm (property*)>
122
+ <!ATTLIST auth-realm name CDATA #REQUIRED
123
+ classname CDATA #REQUIRED>
124
+
125
+ <!-- Syntax for supplying properties as name value pairs -->
126
+ <!ELEMENT property EMPTY>
127
+ <!ATTLIST property name CDATA #REQUIRED
128
+ value CDATA #REQUIRED>
129
+
130
+ <!--
131
+ The message-layer entity is used to define the value of the
132
+ auth-layer attribute of message-security-config elements.
133
+
134
+ Used in: message-security-config
135
+ -->
136
+ <!ENTITY % message-layer "(SOAP)">
137
+
138
+ <!--
139
+ The message-security-config element defines the message layer
140
+ specific provider configurations of the application server.
141
+
142
+ All of the providers within a message-security-config element
143
+ must be able to perform authentication processing at
144
+ the message layer defined by the value of the auth-layer
145
+ attribute.
146
+
147
+ The default-provider attribute may be used to identify
148
+ the server provider to be invoked for any application
149
+ for which a specific server provider has not been bound.
150
+
151
+ The default-client-provider attribute may be used to identify
152
+ the client provider to be invoked for any application
153
+ for which a specific client provider has not been bound.
154
+
155
+ At most one (non-null) default server provider and at most one
156
+ (non-null) default client provider may be identified
157
+ among all the same layer message-security-config elements.
158
+
159
+ When a default provider of a type is not defined for a message
160
+ layer, the container will only invoke a provider of the type
161
+ (at the layer) for those applications for which a specific
162
+ provider has been bound.
163
+
164
+ Default:
165
+ Used in: security-service
166
+ -->
167
+ <!ELEMENT message-security-config ( provider-config+ )>
168
+ <!ATTLIST message-security-config
169
+ auth-layer %message-layer; #REQUIRED
170
+ default-provider CDATA #IMPLIED
171
+ default-client-provider CDATA #IMPLIED>
172
+
173
+ <!--
174
+ The provider-config element defines the configuration of
175
+ an authentication provider.
176
+
177
+ The provider-id attibute contains an identifier that can be used to
178
+ reference the provider-config.
179
+
180
+ The request-policy and response-policy sub-elements define
181
+ the authentication policy requirements associated
182
+ with the request and response processing performed by the
183
+ authentication provider (respectively).
184
+
185
+ the provider-type attribute defines whether the provider is a client
186
+ authentication provider or a server authentication provider.
187
+
188
+ The class-name attribute defines the java implementation class of the
189
+ provider. Client authentication providers must implement the
190
+ com.sun.enterprise.security.jauth.ClientAuthModule interface. Server-side
191
+ providers must implement the com.sun.enterprise.security.jauth.ServerAuthModule
192
+ interface. A provider may implement both interfaces, but it must implement
193
+ the interface corresponding to its provider type.
194
+
195
+ The optional list of property elements may be used to configure provider
196
+ specific property values. These values will be passed to the provider
197
+ when its initialize method is called.
198
+
199
+ A provider-config with no contained request-policy or response-policy
200
+ sub-elements, is a null provider. The container will not instantiate
201
+ or invoke the methods of a null provider, and as such the implementation
202
+ class of a null provider need not exist.
203
+
204
+ Default:
205
+ Used in: message-security-config
206
+ -->
207
+ <!ELEMENT provider-config ( request-policy?, response-policy?, property* )>
208
+ <!ATTLIST provider-config
209
+ provider-id CDATA #REQUIRED
210
+ provider-type (client | server | client-server) #REQUIRED
211
+ class-name CDATA #REQUIRED>
212
+
213
+ <!--
214
+ The request-policy element is used to define the authentication policy
215
+ requirements associated with the request processing performed by an
216
+ authentication provider (i.e. when a client provider's
217
+ ClientAuthModule.initiateRequest method is called or when a
218
+ server provider's ServerAuthModule.validateRequest is called).
219
+
220
+ The auth-source attribute defines a requirement for message layer
221
+ sender authentication (e.g. username password) or content authentication
222
+ (e.g. digital signature).
223
+
224
+ The auth-recipient attribute defines a requirement for message
225
+ layer authentication of the reciever of a message to its sender (e.g. by
226
+ XML encryption).
227
+
228
+ The before-content attribute value indicates that recipient
229
+ authentication (e.g. encryption) is to occur before any
230
+ content authentication (e.g. encrypt then sign) with respect
231
+ to the target of the containing auth-policy.
232
+
233
+ Default:
234
+ Used in: provider-config
235
+ -->
236
+ <!ELEMENT request-policy EMPTY >
237
+ <!ATTLIST request-policy
238
+ auth-source (sender | content) #IMPLIED
239
+ auth-recipient (before-content | after-content) #IMPLIED>
240
+ <!--
241
+ The response-policy element is used to define the authentication policy
242
+ requirements associated with the response processing performed by an
243
+ authentication provider (i.e. when a client provider's
244
+ ClientAuthModule.validateResponse method is called or when a
245
+ server provider's ServerAuthModule.secureResponse method is called).
246
+
247
+ The auth-source attribute defines a requirement for message layer
248
+ sender authentication (e.g. username password) or content authentication
249
+ (e.g. digital signature).
250
+
251
+ The auth-recipient attribute defines a requirement for message
252
+ layer authentication of the reciever of a message to its sender (e.g. by
253
+ XML encryption).
254
+
255
+ The before-content attribute value indicates that recipient
256
+ authentication (e.g. encryption) is to occur before any
257
+ content authentication (e.g. encrypt then sign) with respect
258
+ to the target of the containing auth-policy.
259
+
260
+ Default:
261
+ Used in: provider-config
262
+ -->
263
+ <!ELEMENT response-policy EMPTY >
264
+ <!ATTLIST response-policy
265
+ auth-source (sender | content) #IMPLIED
266
+ auth-recipient (before-content | after-content) #IMPLIED>
267
+