Discussion :

[geforce]

Bonjour,

j'ai une application qui tourne par défaut sur le port 8080 utilisant une authentification BASIC, et que si je démarre avec un autre port (par exemple 8082) la boite de dialogue d'authentification ne s'affiche !! (j'ai pas de message d'erreur).

ce que j'ai fait : crée une petite application vide avec jute l'authentification (web.xml) qui fonction bien et qui fonctionne aussi quand en change de port !!!

Donc je me demande si le probléme viens de mon application ? (mais quoi ! y t'il quelqu'un qui peu aidé a trouvé une solution ?)


Mon Web.xml de mon application :

Code :

Sélectionner tout - Visualiser dans une fenêtre à part

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
<?xml version="1.0" encoding="UTF-8"?>
<web-app id="WebApp_ID" version="3.0"
 xmlns="http://java.sun.com/xml/ns/javaee"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd">
 <display-name>MidatService2</display-name>
 <context-param>
  <param-name>resteasy.jndi.resources</param-name>
  <param-value>java:global/MIDAEAR-1.3-SNAPSHOT/MIDA-1.3-SNAPSHOT/TransfoBean!ireq.beans.TransfoBeanLocal,java:global/MIDAEAR-1.3-SNAPSHOT/MIDA-1.3-SNAPSHOT/FuzzyBean!ireq.beans.FuzzyBeanLocal,java:global/MIDAEAR-1.3-SNAPSHOT/MIDA-1.3-SNAPSHOT/UserBean!ireq.beans.UserBeanLocal</param-value>
 </context-param>
 <context-param>
  <param-name>resteasy.role.based.security</param-name>
  <param-value>true</param-value>
 </context-param>
 <context-param>
  <param-name>resteasy.servlet.mapping.prefix</param-name>
  <param-value>/Service</param-value>
 </context-param>
 <listener>
  <listener-class>org.jboss.resteasy.plugins.server.servlet.ResteasyBootstrap</listener-class>
 </listener>
 <servlet>
  <servlet-name>Resteasy</servlet-name>
  <servlet-class>org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher</servlet-class>
 </servlet>
 <servlet-mapping>
  <servlet-name>Resteasy</servlet-name>
  <url-pattern>/Service/*</url-pattern>
 </servlet-mapping>


 <security-constraint>
  <web-resource-collection>
   <web-resource-name>All resources</web-resource-name>
   <description>Protects all resources</description>
   <url-pattern>/*</url-pattern>
   <http-method>GET</http-method>
   <http-method>POST</http-method>
   <http-method>DELETE</http-method>
   <http-method>PUT</http-method>
  </web-resource-collection>
  <auth-constraint>
   <role-name>Admin</role-name>
   <role-name>Intervenant</role-name>
   <role-name>Superviseur</role-name>
  </auth-constraint>
 </security-constraint>
 <login-config>
  <auth-method>BASIC</auth-method>
  <realm-name>Test Realm</realm-name>
 </login-config>
 <security-role>
  <role-name>Admin</role-name>
 </security-role>
 <security-role>
  <role-name>Intervenant</role-name>
 </security-role>
 <security-role>
  <role-name>Superviseur</role-name>
 </security-role>
</web-app>

[hasalex]

J'ai testé sur une application qui a une authentification basic, et le changement de port n'a pas d'impact. Ça fonctionne.

Est-ce que tu as essayé avec un autre navigateur ?
Quelle version mineure de JBoss AS utilises-tu ?

[geforce]

J'ai testé sur une application qui a une authentification basic, et le changement de port n'a pas d'impact. Ça fonctionne.

Oui moi aussi j'ai la même chose avec un exemple de projet vide avec juste l'authentification basic (je c'est si le probléme viens de application elle mémé)

Est-ce que tu as essayé avec un autre navigateur ?

oui c'est pareille.

Quelle version mineure de JBoss AS utilises-tu ?

JBoss 7.1

[hasalex]

J'avais compris que c'était une 7.1, c'est marqué dans le titre. J'aurais aimé avoir la version précise : 7.1.x.

[geforce]

J'avais compris que c'était une 7.1, c'est marqué dans le titre. J'aurais aimé avoir la version précise : 7.1.x.

ok j'ai utilisé ./run.sh -V c'est donc la : JBoss Application Server 7.1.1

[hasalex]

Et bien je te conseille vivement de passer à la version 7.1.3. Elle corrige plusieurs dizaines de bugs.

[geforce]

Et bien je te conseille vivement de passer à la version 7.1.3. Elle corrige plusieurs dizaines de bugs.

OK, mais je sais pas ce qui c'est passé pour Jboss 7.1.3 (pas disponible sur jbossas.jboss.org) il est juste disponible sur GitHub !! puis il a beaucoup de différence, j'ai peu trouvé que le source et pas le serveur on mode Startup.
Comment ou où je peu trouvé une version stable et en mode Startup de Jboss 7.1.3 ?

Merci

[hasalex]

Il faut faire le build soi-même. Le sujet a déjà été abordé 2 ou 3 fois sur ce forum, mais je me permets quand même un petit rappel : http://blog.alexis-hassler.com/2012/...boss-as-7.html

[geforce]

Il faut faire le build soi-même. Le sujet a déjà été abordé 2 ou 3 fois sur ce forum, mais je me permets quand même un petit rappel : http://blog.alexis-hassler.com/2012/...boss-as-7.html

Je ne c'est pas, mais le build ne fonctionne pas avec le code de Jboss7,1,3 (https://github.com/jbossas/jboss-as/tree/7.1.3.Final) j'ai suivi le tuto du blog !! (J’ai surement malle fait une chose mon targe est incomplet même avec l'option skipTests=true)

[geforce]

voilà le message d'erreur :
initialement avec la commande suivant mvn install -DskipTests

Code :

Sélectionner tout - Visualiser dans une fenêtre à part

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
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
....
[INFO] --- maven-help-plugin:2.1.1:active-profiles (help.active-profiles) @ jbos
s-as-testsuite ---
Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/
maven/plugin-tools/maven-plugin-tools-api/2.4.3/maven-plugin-tools-api-2.4.3.pom
...

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] JBoss Application Server: Build Configuration ...... SUCCESS [ 15.105 s]
[INFO] JBoss Application Server: Parent Aggregator ........ SUCCESS [ 14.496 s]
[INFO] JBoss Application Server: Domain HTTP Interface .... SUCCESS [  0.172 s]
[INFO] JBoss Application Server: Domain HTTP Error Context  SUCCESS [  1.421 s]
[INFO] JBoss Application Server: Protocol Utilities ....... SUCCESS [ 14.746 s]
[INFO] JBoss Application Server: Controller Client ........ SUCCESS [ 16.932 s]
[INFO] JBoss Application Server: Controller Core .......... SUCCESS [ 30.710 s]
[INFO] JBoss Application Server: Domain Management ........ SUCCESS [ 13.059 s]
[INFO] JBoss Application Server: Domain HTTP Interface .... SUCCESS [  6.482 s]
[INFO] JBoss Application Server: Deployment Repository .... SUCCESS [ 17.511 s]
[INFO] JBoss Application Server: Embedded ................. SUCCESS [  5.467 s]
[INFO] JBoss Application Server: Platform MBean integration SUCCESS [  5.451 s]
[INFO] JBoss Application Server: Process Controller ....... SUCCESS [  6.733 s]
[INFO] JBoss Application Server: Network .................. SUCCESS [ 17.713 s]
[INFO] JBoss Application Server: Threading Subsystem ...... SUCCESS [ 57.171 s]
[INFO] JBoss Application Server: Remoting Subsystem ....... SUCCESS [ 42.784 s]
[INFO] JBoss Application Server: Server ................... SUCCESS [04:49 min]
[INFO] JBoss Application Server: Subsystem Test Harness ... SUCCESS [ 53.391 s]
[INFO] JBoss Application Server: JMX Subsystem ............ SUCCESS [ 55.171 s]
[INFO] JBoss Application Server: Naming Subsystem ......... SUCCESS [01:34 min]
[INFO] JBoss Application Server: EE ....................... SUCCESS [02:56 min]
[INFO] JBoss Application Server: JacORB Subsystem ......... SUCCESS [03:20 min]
[INFO] JBoss Application Server: Transaction Subsystem .... SUCCESS [ 44.222 s]
[INFO] JBoss Application Server: Clustering Subsystem ..... SUCCESS [  4.967 s]
[INFO] JBoss Application Server: Clustering Server API .... SUCCESS [ 31.537 s]
[INFO] JBoss Application Server: Common code for clustering subsystems SUCCESS [
  7.201 s]
[INFO] JBoss Application Server: JGroups Subsystem ........ SUCCESS [ 39.379 s]
[INFO] JBoss Application Server: Infinispan Subsystem ..... SUCCESS [01:31 min]
[INFO] JBoss Application Server: Security Subsystem ....... SUCCESS [01:26 min]
[INFO] JBoss Application Server: Connector Subsystem ...... SUCCESS [02:19 min]
[INFO] JBoss Application Server: Clustered registry service SUCCESS [  4.437 s]
[INFO] JBoss Application Server: EJB Subsystem ............ SUCCESS [10:00 min]
[INFO] JBoss Application Server: Distributed Web Session SPI SUCCESS [ 27.008 s]

[INFO] JBoss Application Server: Clustering Server API implementation SUCCESS [
50.079 s]
[INFO] JBoss Application Server: Distributed Web Session Infinispan provider SUC
CESS [ 41.425 s]
[INFO] JBoss Application Server: Web Subsystem ............ SUCCESS [03:38 min]
[INFO] JBoss Application Server: Web Services Subsystem ... SUCCESS [  0.719 s]
[INFO] JBoss Application Server: Web Services Server Integration Subsystem SUCCE
SS [02:45 min]
[INFO] JBoss Application Server: Application Client Bootstrap SUCCESS [01:04 min
]
[INFO] JBoss Application Server: Config Assembly .......... SUCCESS [  7.186 s]
[INFO] JBoss Application Server: Command line interface ... SUCCESS [01:04 min]
[INFO] JBoss Application Server: EJB Client BOM ........... SUCCESS [  0.125 s]
[INFO] JBoss Application Server: JMS Client BOM ........... SUCCESS [  3.623 s]
[INFO] JBoss Application Server: EJB and JMS client combined jar SUCCESS [03:54
min]
[INFO] JBoss Application Server: Clustered Stateful Session Bean cache Infinispa
n provider SUCCESS [ 23.649 s]
[INFO] JBoss Application Server: Clustered service provider registry services SU
CCESS [  7.186 s]
[INFO] JBoss Application Server: Clustered singleton services SUCCESS [ 24.742 s
]
[INFO] JBoss Application Server: EJB Container Managed Persistence Subsystem SUC
CESS [15:26 min]
[INFO] JBoss Application Server: Config Admin ............. SUCCESS [ 26.419 s]
[INFO] JBoss Application Server: Deployment Scanner ....... SUCCESS [01:08 min]
[INFO] JBoss Application Server: EE Deployment ............ SUCCESS [ 39.581 s]
[INFO] JBoss Application Server: JAXR Client .............. SUCCESS [01:41 min]
[INFO] JBoss Application Server: JPA Subsystem ............ SUCCESS [  0.736 s]
[INFO] JBoss Application Server: JPA SPI .................. SUCCESS [01:29 min]
[INFO] JBoss Application Server: JPA UTIL ................. SUCCESS [  3.533 s]
[INFO] JBoss Application Server: JPA Subsystem ............ SUCCESS [ 35.234 s]
[INFO] JBoss Application Server: Weld Integration ......... SUCCESS [01:45 min]
[INFO] JBoss Application Server: JAX-RS Integration ....... SUCCESS [ 52.336 s]
[INFO] JBoss Application Server: JBoss Diagnostic Reporter  SUCCESS [  0.094 s]
[INFO] JBoss Application Server: JDR ...................... SUCCESS [ 37.329 s]
[INFO] JBoss Application Server: JSF Support jar .......... SUCCESS [  7.469 s]
[INFO] JBoss Application Server: JSR-77 Subsystem ......... SUCCESS [ 44.220 s]
[INFO] JBoss Application Server: Management Client Content  SUCCESS [ 18.532 s]
[INFO] JBoss Application Server: Host Controller .......... SUCCESS [05:26 min]
[INFO] JBoss Application Server: Logging Subsystem ........ SUCCESS [01:15 min]
[INFO] JBoss Application Server: Mail subsystem ........... SUCCESS [ 29.262 s]
[INFO] JBoss Application Server: Messaging Subsystem ...... SUCCESS [02:07 min]
[INFO] JBoss Application Server: ModCluster Subsystem ..... SUCCESS [ 40.087 s]
[INFO] JBoss Application Server: OSGi ..................... SUCCESS [  0.093 s]
[INFO] JBoss Application Server: OSGi Subsystem ........... SUCCESS [01:10 min]
[INFO] JBoss Application Server: OSGi ConfigurationAdmin .. SUCCESS [ 23.089 s]
[INFO] JBoss Application Server: POJO Subsystem ........... SUCCESS [01:08 min]
[INFO] JBoss Application Server: sosreport scripts ........ SUCCESS [ 15.419 s]
[INFO] JBoss Application Server: Service Archive Subsystem  SUCCESS [ 34.353 s]
[INFO] JBoss Application Server: XTS Subsystem ............ SUCCESS [ 31.634 s]
[INFO] JBoss Application Server: Hibernate 3.6.x JPA integration SUCCESS [ 23.38
6 s]
[INFO] JBoss Application Server: Hibernate 4.0.x JPA integration SUCCESS [ 31.21
2 s]
[INFO] JBoss Application Server: OpenJPA 2.x JPA integration SUCCESS [ 10.935 s]

[INFO] JBoss Application Server: Build .................... SUCCESS [05:41 min]
[INFO] JBoss Application Server: Arquillian ............... SUCCESS [  2.687 s]
[INFO] JBoss Application Server: Arquillian TestEnricher MSC SUCCESS [ 13.216 s]

[INFO] JBoss Application Server: Arquillian Common ........ SUCCESS [ 34.164 s]
[INFO] JBoss Application Server: Arquillian Protocol JMX .. SUCCESS [ 18.871 s]
[INFO] JBoss Application Server: Arquillian Managed Container SUCCESS [ 35.398 s
]
[INFO] JBoss Application Server: Arquillian Remote Container SUCCESS [  9.967 s]

[INFO] JBoss Application Server: Exported Java EE Specification APIs SUCCESS [
1.281 s]
[INFO] JBoss Application Server: Arquillian TestNG Integration SUCCESS [ 34.757
s]
[INFO] JBoss Application Server: Arquillian Common Domain . SUCCESS [ 14.466 s]
[INFO] JBoss Application Server: Arquillian Remote Domain Container SUCCESS [  8
.560 s]
[INFO] JBoss Application Server: Arquillian Managed Domain Container SUCCESS [ 2
1.730 s]
[INFO] JBoss Application Server: Distribution ............. SUCCESS [ 53.691 s]
[INFO] JBoss Application Server: Remoting Subsystem Test .. SUCCESS [  3.765 s]
[INFO] JBoss Application Server: Validation Tests for Exported Java EE Specifica
tion APIs SUCCESS [  4.483 s]
[INFO] JBoss Application Server: Web Services Tests Integration Subsystem SUCCES
S [  6.952 s]
[INFO] JBoss Application Server Test Suite: Shared ........ SUCCESS [01:37 min]
[INFO] JBoss Application Server Test Suite: Aggregator .... FAILURE [02:10 min]
[INFO] JBoss Application Server Test Suite: Integration ... SKIPPED
[INFO] JBoss Application Server Test Suite: Integration - Smoke SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:47 h
[INFO] Finished at: 2014-10-24T12:27:10-04:00
[INFO] Final Memory: 238M/247M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-help-plugin:2.1.1:
effective-settings (help.effective-settings) on project jboss-as-testsuite: Exec
ution help.effective-settings of goal org.apache.maven.plugins:maven-help-plugin
:2.1.1:effective-settings failed: An API incompatibility was encountered while e
xecuting org.apache.maven.plugins:maven-help-plugin:2.1.1:effective-settings: ja
va.lang.NoSuchMethodError: org.apache.maven.settings.Settings.getRuntimeInfo()Lo
rg/apache/maven/settings/RuntimeInfo;
[ERROR] -----------------------------------------------------
[ERROR] realm =    plugin>org.apache.maven.plugins:maven-help-plugin:2.1.1
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] = file:/C:/Documents%20and%20Settings/dd1786/.m2/repository/org/
apache/maven/plugins/maven-help-plugin/2.1.1/maven-help-plugin-2.1.1.jar
[ERROR] urls[1] = file:/C:/Documents%20and%20Settings/dd1786/.m2/repository/org/
apache/maven/reporting/maven-reporting-api/2.0.6/maven-reporting-api-2.0.6.jar
[ERROR] urls[2] = file:/C:/Documents%20and%20Settings/dd1786/.m2/repository/org/
apache/maven/doxia/doxia-sink-api/1.0-alpha-7/doxia-sink-api-1.0-alpha-7.jar
[ERROR] urls[3] = file:/C:/Documents%20and%20Settings/dd1786/.m2/repository/comm
ons-cli/commons-cli/1.0/commons-cli-1.0.jar
[ERROR] urls[4] = file:/C:/Documents%20and%20Settings/dd1786/.m2/repository/org/
apache/maven/plugin-tools/maven-plugin-tools-api/2.4.3/maven-plugin-tools-api-2.
4.3.jar
[ERROR] urls[5] = file:/C:/Documents%20and%20Settings/dd1786/.m2/repository/jtid
y/jtidy/4aug2000r7-dev/jtidy-4aug2000r7-dev.jar
[ERROR] urls[6] = file:/C:/Documents%20and%20Settings/dd1786/.m2/repository/juni
t/junit/3.8.1/junit-3.8.1.jar
[ERROR] urls[7] = file:/C:/Documents%20and%20Settings/dd1786/.m2/repository/org/
codehaus/plexus/plexus-interactivity-api/1.0-alpha-4/plexus-interactivity-api-1.
0-alpha-4.jar
[ERROR] urls[8] = file:/C:/Documents%20and%20Settings/dd1786/.m2/repository/org/
codehaus/plexus/plexus-utils/1.5.7/plexus-utils-1.5.7.jar
[ERROR] urls[9] = file:/C:/Documents%20and%20Settings/dd1786/.m2/repository/jdom
/jdom/1.0/jdom-1.0.jar
[ERROR] urls[10] = file:/C:/Documents%20and%20Settings/dd1786/.m2/repository/com
/thoughtworks/xstream/xstream/1.3/xstream-1.3.jar
[ERROR] urls[11] = file:/C:/Documents%20and%20Settings/dd1786/.m2/repository/xpp
3/xpp3_min/1.1.4c/xpp3_min-1.1.4c.jar
[ERROR] urls[12] = file:/C:/Documents%20and%20Settings/dd1786/.m2/repository/com
mons-lang/commons-lang/2.4/commons-lang-2.4.jar
[ERROR] Number of foreign imports: 1
[ERROR] import: Entry[import  from realm ClassRealm[project>org.jboss.as:jboss-a
s-parent:7.1.3.Final, parent: ClassRealm[maven.api, parent: null]]]
[ERROR]
[ERROR] -----------------------------------------------------
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e swit
ch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please rea
d the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginContaine
rException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command

[ERROR]   mvn <goals> -rf :jboss-as-testsuite
Z:\jboss-as-7.1.3.Final>

[hasalex]

cf. ma réponse sur http://www.developpez.net/forums/d14...s7-1-3-erreur/

[geforce]

Bonjour,

j’utilise JBOSS 7.1.3 après ce changement j'avait espère que mon bug d’authentification sur un autre port que 8080 ce règle par lui même mais c'est pas le cas !!?

je me dit y une influence de mon application qui crée le bug ? ou c'est moi qui a malle fait quelque chose ? MAIS QUOI

tout suggestion sera la bienvenu