[Security] - Security Context has not been set
by lesquivel
Hello,
I am having the following exception when logging in. I am hoping that somebody might have some suggestions to where I might look or check to try and resolve this issue:
| 17:16:45,552 ERROR [JBossWebRealm] Error during authenticate
| java.lang.IllegalStateException: Security Context has not been set
| at org.jboss.web.tomcat.security.SecurityAssociationActions$SetPrincipal
| InfoAction.run(SecurityAssociationActions.java:70)
| at java.security.AccessController.doPrivileged(Native Method)
| at org.jboss.web.tomcat.security.SecurityAssociationActions.setPrincipal
| Info(SecurityAssociationActions.java:270)
| at org.jboss.web.tomcat.security.JBossWebRealm.authenticate(JBossWebReal
| m.java:388)
| at org.apache.catalina.authenticator.FormAuthenticator.authenticate(Form
| Authenticator.java:258)
| at org.apache.catalina.authenticator.AuthenticatorBase.invoke(Authentica
| torBase.java:417)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValv
| e.java:92)
| at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.proce
| ss(SecurityContextEstablishmentValve.java:126)
| at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invok
| e(SecurityContextEstablishmentValve.java:70)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
| ava:127)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
| ava:102)
| at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedC
| onnectionValve.java:158)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
| ve.java:109)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.jav
| a:330)
| at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:436)
| at org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpPro
| tocol.java:384)
| at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:44
| 7)
| at java.lang.Thread.run(Thread.java:619)
I have a custom login config and my own loginModule. I am Extending AbstractLoginModule.
My login-config.xml:
| <policy>
| <!-- MyCompany LOGIN MODULE -->
| <application-policy name="MyCompany-login-module">
| <authentication>
| <login-module code="org.MyCompany.security.auth.MyCompanyLoginModule" flag="required">
|
| </login-module>
|
| </authentication>
| </application-policy>
| </policy>
|
What kind of errors would cause that exception to occur? Could it be a configuration issue? If it is configuration, what or where should I look?
Could it be a code issue in my login module class? If so, what kind of errors in my code could cause this?
Thanks to anyone that replies with any ideas on this.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251926#4251926
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251926
16 years, 8 months
[Installation, Configuration & Deployment] - Initialcontext.lookup fails
by tjansto
afternoon again,
i have a remote swing app that connects via https to a web server that proxies all requests to our brand spanking new jboss 5.1as instance. i can open up a browser and see a proper (i believe) response for the following url: https://my.server.com/invoker/JNDIFactory. if i look at the data returned, i can see that it is http invoker proxy returned in the response is looking at https://my.appserver.com:8443/invoker/JMXInvokerServlet. (my.server.com is the web side that proxies all requests to the my.appserver.com application server.) i can then hit https://my.server.com/invoker/JMXInvokerServlet and get back a response that, again, appears to be legit. when i do this in the context of my swing client, i get the following error:
javax.naming.CommunicationException: Opeation failed [Root exception is java.rmi.ServerException: IOE; nested exception is: java.net.SocketException: Unexpected end of file from server]
the invoker configuration for the client is the same as i have used for years with the jboss 4.x platform, so i don't thing that is at fault. what i am not sure of is how to further debug what i am sure is a configuration problem in the new 5.1 instance. this sounds like there was a failure in the negotiation of the ssl protocol, as all data transferred between the app server and web server, and web server and client is ssl encrypted, but i again, i am not sure where to start digging...
again, thanks for the help in advance,
tom
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251907#4251907
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251907
16 years, 8 months
[Beginner's Corner] - 502 Bad gateway error
by muddu_shafi
I have developed and deployed Coldfusion webservices(using Bludragon for J2ee)in JBoss applications server. but, While invoking this webservices I am experiencing an error "502 Bad Gateway".
For some webservices which take less time the Apache tomcat server(with in JBOSS) returns a valid response(o/p) but for some webservices which take a little extra time(30seconds to 1minutes) for processing it returns a response "502: bad gateway" even before the code has completed processing the request and is trying to send the response.
I have read some where that "socket timeout" directive in Apache tomcat server's configuration file should be increased or is not set right.
Can anyone let me know where to find the file in my installation?
How do I set the variable?
What is default if the variable is not earlier?
How does it work?
Thanks in advance.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251904#4251904
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251904
16 years, 8 months
[EJB] - 502, Bad Gateway.
by muddu_shafi
I have developed and deployed Coldfusion webservices(using Bludragon for J2ee)in JBoss applications server. but, While invoking this webservices I am experiencing an error "502 Bad Gateway".
For some webservices which take less time the Apache tomcat server(with in JBOSS) returns a valid response(o/p) but for some webservices which take a little extra time(30seconds to 1minutes) for processing it returns a response "502: bad gateway" even before the code has completed processing the request and is trying to send the response.
I have read some where that "socket timeout" directive in Apache tomcat server's configuration file should be increased or is not set right.
Can anyone let me know where to find the file in my installation?
How do I set the variable?
What is default if the variable is not earlier?
How does it work?
Thanks in advance.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251902#4251902
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251902
16 years, 8 months
[JBoss AOP Users] - Re: Deploy AOP to jboss 5.1
by kgreenejpmc
Thanks for the feedback. I have another question.
On discovering that the @JobFlow does not work on onMessage, I was very curious as to how annotations such as @TransactionAttribute work on onMessage (as well as other methods). These types of annotations don't seem to require loadtime weaving. In addition, you don't have to do anything special when you compile your classes that use these annotations (which leads me to believe that compile time weaving is not required either).
I did quite a bit of digging and discovered it might have to do with proxies, but I am not sure. I looked at the jboss source code, but did not see anything special in TransactionAttributeImpl.java
I am interested in developing my custom annotation and aspect such that it works like the @TransactionAttribute in that it does not require load time weaving and you don't have to compile your classes in any special way.
Am I correct in assuming that annotations such as @TransactionAttribute don't use compile time or loadtime weaving? If so, could you point me to some sources that would explain how the the code behind the annotation is triggered and executed?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251894#4251894
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251894
16 years, 8 months
[JBoss AOP Users] - Re: Deploy AOP to jboss 5.1
by kgreenejpmc
Thanks for the feedback. I have another question.
On discovering that the @JobFlow does not work on onMessage, I was very curious as to how annotations such as @TransactionAttribute work on onMessage (as well as other methods). These types of annotations don't seem to require loadtime weaving. In addition, you don't have to do anything special when you compile your classes that use these annotations (which leads me to believe that compile time weaving is not required either).
I did quite a bit of digging and discovered it might have to do with proxies, but I am not sure. I looked at the jboss source code, but did not see anything special in TransactionAttributeImpl.java
I am interested in developing my custom annotation and aspect such that it works like the @TransactionAttribute in that it does not require load time weaving and you don't have to compile your classes in any special way.
Am I correct in assuming that annotations such as @TransactionAttribute don't use compile time or loadtime weaving? If so, could you point me to some sources that would explain how the the code behind the annotation is triggered and executed?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251893#4251893
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251893
16 years, 8 months