Como utilizar o JAAS com JBoss Seam?

Bom dia,
Estou tentando utilizar o JAAS numa aplicação Seam e estou sentindo algumas dificuldades.
Segundo eu li na documentação…

…seria apenas alterar o seguinte no components.xml:

…e no app server, no meu caso o jboss 4.0.5(JEMS) no diretório server/default/conf alterei o arquivo login-config.xml colocando a desclaração da minha politica de segurança…que já utilizava nas demais aplicações, ou seja, o problema não pode ser aqui…

quando rodo a aplicação e tento me autenticar recebo a seguinte mensagem no console…

10:16:36,251 INFO [Server] JBoss (MX MicroKernel) [4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339)] Started in 1m:1s:657ms
10:17:26,564 INFO [ServletCacheAdministrator] Created new instance of ServletCacheAdministrator
10:17:26,564 INFO [ServletCacheAdministrator] Created new application-scoped cache at key: __oscache_cache
10:17:26,705 INFO [Lifecycle] starting up: org.jboss.seam.security.identity
10:17:28,767 ERROR [STDERR] 09/10/2007 10:17:28 com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/D:/java/server/jboss-4.0.5.GA_EJB/server/default/./tmp/deploy/tmp33169jprounidademedida-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jstl-fn.taglib.xml
10:17:28,845 ERROR [STDERR] 09/10/2007 10:17:28 com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/D:/java/server/jboss-4.0.5.GA_EJB/server/default/./tmp/deploy/tmp33169jprounidademedida-exp.war/WEB-INF/lib/ajax4jsf-1.1.1-SNAPSHOT.jar!/META-INF/a4j.taglib.xml
10:17:28,892 ERROR [STDERR] 09/10/2007 10:17:28 com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/D:/java/server/jboss-4.0.5.GA_EJB/server/default/./tmp/deploy/tmp33169jprounidademedida-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-core.taglib.xml
10:17:28,908 ERROR [STDERR] 09/10/2007 10:17:28 com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/D:/java/server/jboss-4.0.5.GA_EJB/server/default/./tmp/deploy/tmp33169jprounidademedida-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-html.taglib.xml
10:17:28,908 ERROR [STDERR] 09/10/2007 10:17:28 com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/D:/java/server/jboss-4.0.5.GA_EJB/server/default/./tmp/deploy/tmp33169jprounidademedida-exp.war/WEB-INF/lib/jboss-seam-pdf.jar!/META-INF/seam-pdf.taglib.xml
10:17:28,939 ERROR [STDERR] 09/10/2007 10:17:28 com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/D:/java/server/jboss-4.0.5.GA_EJB/server/default/./tmp/deploy/tmp33169jprounidademedida-exp.war/WEB-INF/lib/jboss-seam-mail.jar!/META-INF/seam-mail.taglib.xml
10:17:29,001 ERROR [STDERR] 09/10/2007 10:17:29 com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/D:/java/server/jboss-4.0.5.GA_EJB/server/default/./tmp/deploy/tmp33169jprounidademedida-exp.war/WEB-INF/lib/richfaces-3.0.1-SNAPSHOT.jar!/META-INF/rich.taglib.xml
10:17:29,642 ERROR [STDERR] 09/10/2007 10:17:29 com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/D:/java/server/jboss-4.0.5.GA_EJB/server/default/./tmp/deploy/tmp33169jprounidademedida-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jstl-core.taglib.xml
10:17:29,689 ERROR [STDERR] 09/10/2007 10:17:29 com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/D:/java/server/jboss-4.0.5.GA_EJB/server/default/./tmp/deploy/tmp33169jprounidademedida-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-ui.taglib.xml
10:17:29,705 ERROR [STDERR] 09/10/2007 10:17:29 com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/D:/java/server/jboss-4.0.5.GA_EJB/server/default/./tmp/deploy/tmp33169jprounidademedida-exp.war/WEB-INF/lib/jboss-seam-ui.jar!/META-INF/seam-ui.taglib.xml
10:17:39,892 INFO [RendererUtils] Unable to find component ‘username’ (calling findComponent on component ‘login:_id18’). We’ll try to return a guessed client-id anyways - this will be a problem if you put the referenced component into a different naming-container. If this is the case, you can always use the full client-id.
10:17:39,892 INFO [MyfacesConfig] No context init parameter ‘org.apache.myfaces.PRETTY_HTML’ found, using default value true
10:17:39,892 INFO [MyfacesConfig] No context init parameter ‘org.apache.myfaces.ALLOW_JAVASCRIPT’ found, using default value true
10:17:39,892 INFO [MyfacesConfig] Tomahawk jar not available. Autoscrolling, DetectJavascript, AddResourceClass and CheckExtensionsFilter are disabled now.
10:17:39,908 INFO [RendererUtils] Unable to find component ‘password’ (calling findComponent on component ‘login:_id20’). We’ll try to return a guessed client-id anyways - this will be a problem if you put the referenced component into a different naming-container. If this is the case, you can always use the full client-id.
10:17:42,549 INFO [RendererUtils] Unable to find component ‘username’ (calling findComponent on component ‘login:_id18’). We’ll try to return a guessed client-id anyways - this will be a problem if you put the referenced component into a different naming-container. If this is the case, you can always use the full client-id.
10:17:42,564 INFO [RendererUtils] Unable to find component ‘password’ (calling findComponent on component ‘login:_id20’). We’ll try to return a guessed client-id anyways - this will be a problem if you put the referenced component into a different naming-container. If this is the case, you can always use the full client-id.
10:17:48,689 INFO [RendererUtils] Unable to find component ‘username’ (calling findComponent on component ‘login:_id18’). We’ll try to return a guessed client-id anyways - this will be a problem if you put the referenced component into a different naming-container. If this is the case, you can always use the full client-id.
10:17:48,689 INFO [RendererUtils] Unable to find component ‘password’ (calling findComponent on component ‘login:_id20’). We’ll try to return a guessed client-id anyways - this will be a problem if you put the referenced component into a different naming-container. If this is the case, you can always use the full client-id.

Pra ser bem sincero eu não compreendi muito bem o que o container tah tentando me falar
Alguém sabe o que tah acontecendo aqui ?
Agradeço a ajuda !

Topicos relacionados