[JBoss Portal] - LDAPExtUserModuleImpl and userSearchFilter
by roth
Hi
I setting up a portal with LDAPExtUserModuleImpl with Microsoft Active Directory. So far, everything is going along nicely. I am already able to authenticate against my AD, and I am now working on authorisation and integrating roles. I'll post my config files once everything is working.
Now, the following small problem showed up:
In ldap_identity-config.xml, I have
| <option>
| <name>userSearchFilter</name>
| <value>(&(sAMAccountName={0})(objectClass=User))</value>
| </option>
|
This gives me the following error:
| --- MBeans waiting for other MBeans ---
| ObjectName: portal:service=Module,type=IdentityServiceController
| State: FAILED
| Reason: org.jboss.portal.identity.IdentityException: Cannot parse identity configuration file
|
If I change the filter to a mere
| (sAMAccountName={0})
|
everything works like a charm.
Is this a bug, or am I doing something wrong with that filter?
I am using Jboss 4.3.0 and JBoss_Portal_2_6_0 from svn.
Thanks,
Tobias
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4063368#4063368
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4063368
18Â years, 11Â months
[JBoss jBPM] - Re: Problem with multiple end-states
by efip10
I use multiple end-states, and it works.
As outlined in "Node responsibilities" in userguide, only the node action can decide on which transition to take. In event action, you cannot take this decision.
<node name="check-suspend-or-abort">
| <action class="com.qq.DecideIfSuspendedOrAbortedAction" />
| <transition to="continue" />
| <transition to="error" name="error"/>
| <transition to="suspended" name="suspended"/>
| <transition to="aborted" name="aborted"/>
| </node>
|
| <end-state name="aborted">
| </end-state>
|
| <end-state name="suspended">
| </end-state>
|
| <end-state name="error">
| </end-state>
|
Here's the action:
public void execute(ExecutionContext ctx) throws Exception {
| Map params = ctx.getContextInstance().getVariables();
|
| // check if aborted - invoke my function
| if (isAbortedFlagForWorkflow()) {
| // do something
| ctx.getToken().signal("aborted");
| } else
| // check if suspended
| if (isSuspendedFlagForWorkflow()) {
| // do something
| ctx.getToken().signal("suspended");
| } else {
| // everything is OK, we may start the workflow
| // leave over default transition
| ctx.getToken().signal();
| }
| }
|
Hope it helps.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4063364#4063364
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4063364
18Â years, 11Â months