Archive for April 2015

In this article I will be describing how to add a secondary LDAP userstore to WSO2 Identity Server 5.0, Apache Directory Studio 2.0. Download and extract both the products to a desired location.

using

Create a Userstore in Apache DS

First we need to create a LDAP Userstore in Apache DS. For that Start Apache DS and create a New LDAP Connection, which will prompts the following wondow.

Give localhost to Hostname and 389 for Port (this is the default), and a desired name for the Connection. Click Next once done.

In the next wondow, select loging credential for the LDAP connection. Here I will be giving "cn=admin,dc=supun,dc=com" as "Bind DN or user" and "supun" as the Bind password. Click finish once done.

Then in the LDAP browser, create a user(s) in the following structure.

Adding the Secondary Userstore to WSO2 IS

Start WSO2 IS server by navigating to <IS_HOME>/bin and executing ./wso2server.sh (in ubuntu). Login to the carbon console with super-user credentials.

Navigate to Configure > User Store Management, and click on "Add Secondary User Store"

In the next window, give the the following configurations, which are according to the userstore we created earlier using Apache DS.

Domain Name: any desired value

Connection Name: This is should be the exact value we gave to "Bind DN or user" in Apache DS. (i.e. in this case it chould be "cn=admin,dc=supun,dc=com" )

Connection URL: This should be "ldap://localhost:389" where localhost and 389 refers to the hostane and the port we set in Apache DS.

Connection Password: The value we set to "Bind password" when creating the LDAP connection is Apache DS. (in our case it is "supun").

User Search Based: This should be the DN of the context under which user entries are stored in LDAP in Apache DS. According to the structure we created earlier our user (supun) is listed under ou=users of user group ou=userGroup, which is again listed under dc=supun,dc=com. Therefore, value for this should be "ou=users,ou=userGroup,dc=supun,dc=com".

User Object Class: (objectClass=person)

Username Attribute: uid

User Search Filter: (&(objectClass=person)(uid=?))

Group Search Base: ou=users,ou=userGroup,dc=supun,dc=com

Group Name Attribute: ou

Group Object Class: (objectClass=groupOfNames)

Group Search Filter: (&(objectClass=groupOfNames)(ou=?))

And in the "optional" tab (can found right after the above properties), set the User DN Pattern pattern to DN where the users are listed. (Or a DN that matches to a top level in the hierachy where the users are listed). In this case, it should be set to "ou=userGroup,dc=supun,dc=com".

Leave the rest of the options as it is. Click add once everything is complete. Refresh the page after a couple of seconds and you should see the newly created userstore being listed in the same page.

Then navigate to Configure > Users and Roles > Users. If everything went well, you should see the user we created in the LDAP is being listed down here. (SECONDARY.STORE/supun)

Modify the Claim Mappings

Eventhough our user is listed as above, if you try to view and update the user profile, you might encounter with server errors saying certain attributes are not being supported by the underlying LDAP. This occurs because of the user claims have not being properly mapped with the attributes of the user in out LDAP. For this, we need to update the user-claims. To that go to Claim management and click on http://wso2.org/claims.

Then you would see the list of claims that are available (see below). Then click on any of the claims which you want to modifiy, and click edit.

Wrote by Supun Setunga

In this article I will be describing how to setup a hadoop file system in the local machine to run in Pseudo-Distributed mode. First download hadoop form here.

Then extract it to any preffered location. Now we need to send the environment variables to this extracted location. For that open open ~/.bashrc file and add the following to two separate lines.

export HADOOP_HOME=/home/supun/Supun/Softwares/hadoop-2.2.0

export PATH=/home/supun/Supun/Softwares/hadoop-2.2.0/bin:$PATH

Where /home/supun/Supun/Softwares/hadoop-2.2.0 is the location of my hadoop file was extracted. I will be refering this location as HADOOP_HOME from here onwards.

Configuring:

Now we need to make some small configurations for the following files. Open each of the file and add the following to them.

HADOOP_HOME/conf/core-site.xml

<configuration>
<property>
<name>fs.default.name</name>

<value>hdfs://localhost:9000</value>

</property>

</configuration>

HADOOP_HOME/conf/hdfs-site.xml

<name>dfs.replication</name>

</property>

</configuration>

HADOOP_HOME/conf/mapred-site.xml

<name>mapred.job.tracker</name>

<value>localhost:9001</value>

</property>

</configuration>

Optional:

Check whether ssh is installed in the machine by executing "which ssh" and "which sshd". If ssh/sshd has not being installed. install them using:

sudo apt-get install ssh

Now if the software is installed, try the following command (ubuntu) to check whether ssh can access the localhost without a password.

ssh localhost

If this asks for a password (local machine's user's password), then execute the following.

ssh-keygen -t dsa -P '' -f ~/.ssh/id_dsa

cat ~/.ssh/id_dsa.pub >> ~/.ssh/authorized_keys

Start in Pseudo-Distributed mode

Before start the hdfs, you need to format the namenode. For that, navigate to HADOOP_HOME/bin directory and execute the following.

hdfs namenode -format

Then start the hdfs by navigateing to HADOOP_HOME/sbin and executing the following.

./start-dfs.sh

Or if it didn't work, try executing "./start-dfs.sh -upgrade", instead of above.

If everything goes well, hdfs should be started. And you can browse the webUI of the name node from the URL: http://localhost:50070/dfshealth.jsp. Please refer [1] for further details on setting up hdfs in different modes.

Now you can use hadoop shell commands to manage files in this hdfs. Refer [2] and [3] for Hadoop Commands.