[JBoss Transactions Development] - proposal for Xid format change
by jhalliday
Xid creation is somewhat slow at present and misses the opportunity to encode some useful information. I propose some changes.
Old version:
gtrid = nodename.getBytes()+"#"+tx_uid.stringForm().getBytes();
bqual = new Uid().stringForm().getBytes();
Converting Uids to string form is expensive and should be avoided as we are just going to convert it straight back to binary anyhow. The only advantage of the string form is it makes Xid.toString easy. However, it's better to avoid the overhead on Xid creation and move it to Xid.toString instead i.e. decode the data back in to a Uid in toString.
I was mulling over moving nodename from String to int for similar reasons, but I'm scrapping that idea in favor of just cleaning up the code so it uses a fixed charset - right now bad things happen if the encoding and decoding take place on systems with different default charset.
The branch qualifier should be extended to encode the EIS ID of the XAResource the branch is being created for, if it's available. This will help in new versions of the server, where the JCA should supply a meaningful EIS ID (e.g. the JNDI name of the Datasource) so that Xids/XAResourceRecords can then be matched to data sources.
This is useful for diagnosing failures. It's also handy in recovery situations - if you have a record with a specific EIS ID and also a current XAResource with the same, then if the recovery pass on that resource does not include the Xid as in-doubt, you can conclude the tx completed but the tx manager crashed before removing its log file. Currently there is insufficient information to draw that conclusion, making cleaning up the log file a more risky proposition.
Thus we arrive at the new version:
gtrid = nodename.getBytes("UTF-8")+"#"+UidHelper.getBytes(tx_uid);
bqual = eisId.getBytes("UTF-8")+#"+UidHelper.getBytes(new Uid());
Comments?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262722#4262722
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262722
15 years, 3 months
[JBoss Portal Development] - Jboss - Windows Active Directory Integration - Urgent
by arunicbe
I am integrating Jboss Portal server 2.7.2 with Microsoft Windows server 2003 active directory ldap.
I followed the steps provided in the wiki configportalforMicrosoftactivedirectory.
When I open the portal, it throws the error "User Search Failed". I am unable to proceed. I have provided the contents of ldap_identity-config.xml at the bottom.
I have two questions:
1. Is this config correct?
2. I created two organisational units in my active directory namely
People and Roles. Do I need to create admin user in any of these
OUs. Do we need to create any groups under Roles OU.
Any help is highly appreciated.
Thanks.
Contents of my ldap_identity-config.xml:
<?xml version="1.0" encoding="UTF-8"?>
<!--~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~ JBoss, a division of Red Hat ~
~ Copyright 2006, Red Hat Middleware, LLC, and individual ~
~ contributors as indicated by the @authors tag. See the ~
~ copyright.txt in the distribution for a full listing of ~
~ individual contributors. ~
~ ~
~ This is free software; you can redistribute it and/or modify it ~
~ under the terms of the GNU Lesser General Public License as ~
~ published by the Free Software Foundation; either version 2.1 of ~
~ the License, or (at your option) any later version. ~
~ ~
~ This software is distributed in the hope that it will be useful, ~
~ but WITHOUT ANY WARRANTY; without even the implied warranty of ~
~ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU ~
~ Lesser General Public License for more details. ~
~ ~
~ You should have received a copy of the GNU Lesser General Public ~
~ License along with this software; if not, write to the Free ~
~ Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA ~
~ 02110-1301 USA, or see the FSF site: http://www.fsf.org. ~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~-->
<!--<!DOCTYPE identity-configuration PUBLIC
"-//JBoss Portal//DTD JBoss Identity Configuration 1.0//EN"
"http://www.jboss.org/portal/dtd/identity-config_1_0.dtd">-->
<!-- This file overrides settings from standardidentity-config.xml.
Check default option values that are used there -->
<identity-configuration>
LDAP
host
myip
port
389
adminDN
myadmin
adminPassword
myadminpassword
<!--
protocol
ssl
-->
<!--type used to correctly map in IdentityContext registry-->
User
LDAP
<!--Use this implementation for more flexible user retrieval-->
org.jboss.portal.identity.ldap.LDAPExtUserModuleImpl
Role
LDAP
<!--Use this implementation for more flexible user retrieval-->
org.jboss.portal.identity.ldap.LDAPExtRoleModuleImpl
Membership
LDAP
org.jboss.portal.identity.ldap.LDAPStaticGroupMembershipModuleImpl
UserProfile
DELEGATING
ldapModuleJNDIName
java:/portal/LDAPUserProfileModule
DBDelegateUserProfile
DB
randomSynchronizePassword
true
LDAPDelegateUserProfile
LDAP
<option-group>
<group-name>common</group-name>
userCtxDN
ou=People,ou=Roles,dc=caro,dc=com
uidAttributeID
sAMAccountName
userSearchFilter
<![CDATA[(&(sAMAccountName={0})(objectClass=User))]]>
roleCtxDN
<![CDATA[ou=People,ou=Roles,dc=caro,dc=com]]>
roleSearchFilter
<![CDATA[(&((CN={0})(objectClass=group)))]]>
searchScope SUBTREE_SCOPE
</option-group>
</identity-configuration>
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262700#4262700
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262700
15 years, 3 months