Impersonation in GateIn Portal
by Marek Posolda
Hi all,
We've been requested several times by our users/customers to add
"impersonation" feature.
It may be useful for portal administrator to have possibility to
temporary login as another user without knowing his password. For
example: User /root/ wants to verify that user /mary/ really doesn't
have permission to see page X or portlet Y on page Z.
I've added specification page here
https://community.jboss.org/wiki/ImpersonationInGateInPortal . Feel free
to provide feedback here or in comments of specification.
Have a nice weekend!
Marek
12 years, 4 months
Intellij license
by Julien Viet
It should expire next week.
I asked for a one year renewal.
I'll keep you informed.
Julien
12 years, 9 months
Goodbye
by Christophe Laprun
Hi all,
It is with mixed emotions that I finally write this email. Today is my last day at Red Hat after almost 8 years. I joined in the old JBoss days to work on JBoss Portal and, having gone through lots of revisions (and several product names to seemingly come back to JBoss Portal ^_^), I felt it was time for me to do something new and tackle new challenges.
So, mixed emotions because I will miss working at Red Hat (though I won't be missing BugZilla much) mostly because of the talented people I got to work with daily and, even though we rarely met face to face, I will miss the camaraderie that we had in the Portal team, the satisfaction we got delivering a great product (almost) always on time despite tight schedules and last minute client RFEs or bugs uncovered by our ever excellent QA team! I will also miss my interactions with the support guys and gals who always helped tremendously scope and fix customer issues. "Thank you" barely scratches the surface of my gratitude but thank you nevertheless! On the other hand, I'm obviously excited to work on new things and hopefully work with new people as well but my JBoss / Red Hat years will definitely remain special.
If you feel so inclined (or need to get in touch with me regarding WSRP ^_^), I can be reached at metacosm(a)gmail.com. Find me on LinkedIn or twitter as well (@metacosm).
I wish the best to all of you and may our paths cross again in the future!
Cordialement / Best,
Chris
==
Principal Software Engineer / JBoss Enterprise Middleware Red Hat, Inc.
Follow GateIn: http://blog.gatein.org / http://twitter.com/gatein
Follow me: http://twitter.com/metacosm
12 years, 10 months
Portlet maximization
by Marko Strukelj
We found some maximization issues when implementing a certain use case
where there is one custom navigation portlet (unrelated to portal
navigation), controlling which of several instances of another custom
portlet within the same page should be maximized. So - you have portlet A
commanding portlets B1, B2, B3 via portlet events which one of them is the
maximized one, and that one has to set its own window state to Maximized.
At the same time any other already maximized has to become minimized - the
second part has to be enforced by PC.
We needed to make several fixes to get the scenario working.
https://github.com/gatein/gatein-portal/pull/609
https://github.com/gatein/gatein-pc/pull/10
Besides the need to review these patches by someonw with mor eintimate
knowledge of the codebase, there are some questions about this. For example
- what is the role of UIPageBody, and why both UIPage, and UIPageBody have
a maximized component set independently of each other - to support our case
we had to update in both places to make it work, as some checks look at
one, and other checks at the other for the complete processing to get
through properly, and since you can only have one maximized component
within a page it seems like a bug for the two places to be able to get out
of sync.
I'm adding Adam Kovari, who did most of the work on this.
- marko
12 years, 10 months
Can't start GateIn trunk in clustered mode
by Tuyen The Nguyen
Hi all, I'm working on issue GTNPORTAL-2258.
I configure Gatein cluster mode follow by document of gatein (
https://docs.jboss.org/author/display/GTNPORTAL35/Clustering+configuration).
When i start gatein with command:
$ ./bin/standalone.sh --server-config=standalone-ha.xml -
Djboss.node.name=node1 -b 192.168.210.101 -u 2.439.232.2
-Djboss.bind.address.management=192.168.210.101
I can't understand param "-u 239.23.42.2", i see that's multicast IP, but
how can i get this ip in my network.
When i remove this param and use default of jbossAS and it work with gatein
3.5.x But in 3.6.x and master branch, i always meet exception.
*Is there anybody know how to fix this bug?*
*Exception:*
ERROR [org.jgroups.protocols.UDP] (Timer-2,127.0.0.1:56200) failed sending
message to null (66 bytes): java.lang.Exception: dest=/230.0.0.4:45588 (69
bytes)
at org.jgroups.protocols.UDP._send(UDP.java:374)
at org.jgroups.protocols.UDP.sendToAllMembers(UDP.java:302)
at org.jgroups.protocols.TP.doSend(TP.java:1478)
at org.jgroups.protocols.TP.send(TP.java:1468)
at org.jgroups.protocols.TP.down(TP.java:1186)
at org.jgroups.protocols.TP$ProtocolAdapter.down(TP.java:2308)
at org.jgroups.protocols.PING.sendMcastDiscoveryRequest(PING.java:278)
at org.jgroups.protocols.PING.sendGetMembersRequest(PING.java:259)
at org.jgroups.protocols.Discovery$PingSenderTask$1.run(Discovery.java:407)
at org.jgroups.util.TimeScheduler$RobustRunnable.run(TimeScheduler.java:196)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
[rt.jar:1.6.0_45]
at
java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
[rt.jar:1.6.0_45]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
[rt.jar:1.6.0_45]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
[rt.jar:1.6.0_45]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
[rt.jar:1.6.0_45]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
[rt.jar:1.6.0_45]
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
[rt.jar:1.6.0_45]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
[rt.jar:1.6.0_45]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_45]
Caused by: java.io.IOException: Invalid argument
at java.net.PlainDatagramSocketImpl.send(Native Method) [rt.jar:1.6.0_45]
at java.net.DatagramSocket.send(DatagramSocket.java:625) [rt.jar:1.6.0_45]
at org.jgroups.protocols.UDP._send(UDP.java:358)
... 18 more
12 years, 10 months
* membership
by Julien Viet
Hi,
in the scope of GateIn 3.7 we want to introduce a new feature that is related to the organization service. It will be implemented partly in Core and also in PicketLink organization service implementation.
The current behavior and changes we want to implement are documented here : https://community.jboss.org/wiki/SupportForWildcardMembershipType
We can discuss here any concern about this feature.
cheers
Julien
12 years, 11 months
Resolved NodePath in PortalRequestContext
by Nick Scavelli
TLDR: eXo.env.server.portalBaseURL and eXo.env.server.portalURLTemplate
have changed to include only the resolved path.
I've made a change (http://git.io/ogoWhw) which has only been applied to
master so it can resonate a bit in hopes there are no issues. I have
added a resolvedNodePath field to PortalRequestContext (even though I
think nodePath should be changed) to represent the resolved path of the
portal. Meaning if I go to URL /portal/classic/home/foo the resolved
path is just /home not /home/foo.
The reason for this change was that a fix was applied to decode the
nodePath in order to avoid XSS in the URL since we use this value to
create the JavaScript variables eXo.env.server.portalBaseURL and
eXo.env.server.portalURLTemplate. However this caused an issue for
non-ascii node names since the route couldn't be found after decoding. I
think the resolvedNodePath is a better solution however it does change
the behavior of the JS variables I mentioned.
If anyone sees a potential issue with this solution please discuss here.
- Nick
12 years, 11 months
