[JBoss Portal Users] - Re: Role based landing page/portal for user
by vivek_saini07
Well... 4 months old thread!! what made u posting here after so long time??
Had you asked me it four months back, I would have told u this in more detail as I had lots of time (and energy) at that time.
In short, we did it by modifying customizationManagerService. There are number of threads in this forum explaining how to do this.
In that class somewhere it is written that a portal named "Template" would always be copied to dashboard of logged in user.
U can change that piece, some conditional tweak........... on certain condition copy this portal ....otherwise copy some other portal.
We maintained a table in DB that had mapping between users and their portal.
And after doing all this, there is a property in property file of "conf" folder (this is documented in reference guide) by setting that property user will always land to his dashboard after log-in instead of (public)portal.
Hope this would help.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4252110#4252110
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4252110
16 years, 8 months
[Security] - Custom Authorization
by bacooper81
Hi. Is it possible to take a principal that I authorize in my own servlet and somehow stuff it into the JBoss container (or wherever it needs to go) so that the user remains logged in for the duration of the session? If so, how can that be done?
Basically, I'd like to bypass the FORM authentication mechanism because I have custom code I need to use to handle redirecting the user after logging in.
I've done a LOT of reading on this so far, and haven't found a way. Several people mention creating an InitialContext, logging into it, and calling EJB methods with it. The problem is that the user won't stay logged in for the entire session.
Thanks.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4252108#4252108
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4252108
16 years, 8 months
[JBoss Remoting Users] - Weird port number on connection fail
by chipschoch
We are running JBossAS 4.2.2 with JBM 1.4.4. Recently we experience a problem and I am trying to track it down. It appeared to be a network issue in that we got the following in the log:
2009-08-25 10:45:22,902 ERROR | Thread-24 | org.jboss.remoting.callback.ServerInvokerCa
| llbackHandler | Error handling callback
| org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing so
| cket connection for InvokerLocator [bisocket://10.33.32.22
| :1810191292/callback?callbackServerHost=10.33.32.22&callbackServerPort=1810191292&callbackServerProtocol=bisocket&clientMaxPoolSize=1&clientSocketClass=org.jb
| oss.jms.client.remoting.ClientSocketWrapper&datatype=jms&guid=axwm-58z961-fy0jth8v-1-fy0jumsb-4y&isCallbackServer=true&onewayThreadPool=org.jboss.jms.server.r
| emoting.DirectThreadPool&serverSocketClass=org.jboss.jms.server.remoting.ServerSocketWrapper]
| at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientI
| nvoker.java:548)
| at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvok
| er.java:422)
| at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:141)
| at org.jboss.remoting.Client.invoke(Client.java:1858)
| at org.jboss.remoting.Client.invoke(Client.java:718)
| at org.jboss.remoting.Client.invokeOneway(Client.java:769)
| at org.jboss.remoting.callback.ServerInvokerCallbackHandler.handleCallback(ServerInvokerCall
| backHandler.java:829)
| at org.jboss.remoting.callback.ServerInvokerCallbackHandler.handleCallbackOneway(ServerInvok
| erCallbackHandler.java:700)
| at org.jboss.jms.server.endpoint.ServerSessionEndpoint.performDelivery(ServerSessionEndpoint
| .java:1467)
| at org.jboss.jms.server.endpoint.ServerSessionEndpoint.handleDelivery(ServerSessionEndpoint.
| java:1379)
| at org.jboss.jms.server.endpoint.ServerConsumerEndpoint.handle(ServerConsumerEndpoint.java:3
| 27)
| at org.jboss.messaging.core.impl.RoundRobinDistributor.handle(RoundRobinDistributor.java:119
| )
| at org.jboss.messaging.core.impl.MessagingQueue$DistributorWrapper.handle(MessagingQueue.jav
| a:583)
| at org.jboss.messaging.core.impl.ClusterRoundRobinDistributor.handle(ClusterRoundRobinDistri
| butor.java:79)
| at org.jboss.messaging.core.impl.ChannelSupport.deliverInternal(ChannelSupport.java:670)
| at org.jboss.messaging.core.impl.MessagingQueue.deliverInternal(MessagingQueue.java:506)
| at org.jboss.messaging.core.impl.ChannelSupport.handle(ChannelSupport.java:251)
| at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.routeInternal(MessagingPostO
| ffice.java:2228)
| at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.route(MessagingPostOffice.ja
| va:515)
| at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.sendMessage(ServerConnectionEndpoi
| nt.java:769)
| at org.jboss.jms.server.endpoint.ServerSessionEndpoint.send(ServerSessionEndpoint.java:399)
| at org.jboss.jms.server.endpoint.advised.SessionAdvised.org$jboss$jms$server$endpoint$advise
| d$SessionAdvised$send$aop(SessionAdvised.java:87)
| at org.jboss.jms.server.endpoint.advised.SessionAdvised$send_7280680627620114891.invokeNext(
| SessionAdvised$send_7280680627620114891.java)
| at org.jboss.jms.server.container.SecurityAspect.handleSend(SecurityAspect.java:157)
| at sun.reflect.GeneratedMethodAccessor114.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:121)
| at org.jboss.jms.server.endpoint.advised.SessionAdvised$send_7280680627620114891.invokeNext(
| SessionAdvised$send_7280680627620114891.java)
| at org.jboss.jms.server.endpoint.advised.SessionAdvised.send(SessionAdvised.java)
| at org.jboss.jms.wireformat.SessionSendRequest.serverInvoke(SessionSendRequest.java:95)
| at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandle
| r.java:143)
| at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:862)
| at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:101)
|
| at org.jboss.remoting.Client.invoke(Client.java:1858)
| at org.jboss.remoting.Client.invoke(Client.java:718)
| at org.jboss.remoting.Client.invoke(Client.java:706)
| at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:189)
| at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:160)
| at org.jboss.jms.client.delegate.ClientSessionDelegate.org$jboss$jms$client$delegate$ClientS
| essionDelegate$send$aop(ClientSessionDelegate.java:499)
| at org.jboss.jms.client.delegate.ClientSessionDelegate$send_6145266547759487588.invokeNext(C
| lientSessionDelegate$send_6145266547759487588.java)
| at org.jboss.jms.client.container.SessionAspect.handleSend(SessionAspect.java:661)
| at org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect28.invoke(SessionAspect2
| 8.java)
| at org.jboss.jms.client.delegate.ClientSessionDelegate$send_6145266547759487588.invokeNext(C
| lientSessionDelegate$send_6145266547759487588.java)
| at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.j
| ava:92)
| at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
| at org.jboss.jms.client.delegate.ClientSessionDelegate$send_6145266547759487588.invokeNext(C
| lientSessionDelegate$send_6145266547759487588.java)
| at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
| at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
| at org.jboss.jms.client.delegate.ClientSessionDelegate$send_6145266547759487588.invokeNext(C
| lientSessionDelegate$send_6145266547759487588.java)
| at org.jboss.jms.client.delegate.ClientSessionDelegate.send(ClientSessionDelegate.java)
| at org.jboss.jms.client.container.ProducerAspect.handleSend(ProducerAspect.java:276)
| at org.jboss.aop.advice.org.jboss.jms.client.container.ProducerAspect39.invoke(ProducerAspec
| t39.java)
| at org.jboss.jms.client.delegate.ClientProducerDelegate$send_3961598017717988886.invokeNext(
| ClientProducerDelegate$send_3961598017717988886.java)
| at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
| at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
|
I am particularly curious about the line
callbackServerPort=1810191292
Does this port number look to be correct? If not, could this be the cause of the failure to get a connection?
Thanks alot.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4252091#4252091
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4252091
16 years, 8 months