TOGAF 9.1 Certified


The 2nd part of the TOGAF certification is much different than the 1st exam.  While it’s still multiple choice, there are only 8 scenario based questions.  Furthermore, the answers are weighted so that you can receive partial credit for an incorrect response.

A pass is 60%.

My approach:

I took a similar approach as I did for the 1st exam:

I read the study guide twice and I reviewed it about 5 times after that.


I spent a total of 1 week studying.



Final Thoughts:

While there is a sense of accomplishment in attaining this certification, it is difficult to express an opinion about TOGAF in general without having seen it first hand.


The Project Management Institute Southern Alberta Chapter Professional Development Conference was fantastic for the 2nd year in a row.

Even with a downturn in the economy there was a tremendous turnout with many returning sponsors.

I volunteered as a session host on the first day.  My responsibilities included 2 concurrent sessions.  The 2 speakers for the concurrent sessions were quite knowledgeable and experienced presenters.

All keynote speakers did a really good job.  There was even a common theme around “comfort zone”.  The message was that we should strive to look outside our comfort zone so much so that our discomfort zone becomes our comfort zone.


Looking forward to next year.

TOGAF 9.1 Foundation


The foundation exam is part 1 (of 2) that is required to obtain the TOGAF certification.

There are no pre-requisites and there are no requirements to uphold the certification.  TOGAF is all about establishing an enterprise architecture practice.


The exam is based on the TOGAF study guide.  The foundation guide is not overly lengthy.

The exam is administered through Prometric so you have to attend a nearby testing centre to take the exam.

There are 40 questions and you have 1 hour.  A pass is 55%.

My approach:

I read the study guide twice and I reviewed it about 5 times after that.

I focused on the areas that are highly covered in the exam.  The study guide indicates how many questions are applied to each section.

As long as you have a thorough understanding of ADM, you should be fine.

I spent a total of 1 week studying for this exam.



Final Thoughts:

Each exam is 320 USD.  That may be a consideration before attempting this certification.

I’ll post another blog on the results of part 2 (TOGAF 9.1 Certified):


Insanity Asylum Volume 2

I promised to provide a review on this from my earlier blog Insanity Asylum Volume 1, so here it is…

I ended up doing Volume 2 for most of 2015.  However, I have to be honest.  I was not quite a diligent compared to Volume 1, mostly because of a hamstring injury which hindered me for most of the year.

Overall, Volume 2 is harder than Volume 1.  It focuses more on strength/toning and less on cardio compared to Volume 1.  Also, the workouts are longer.

I liked the format a lot better.  A repeated 7-day regime makes more sense than a 30-day routine to me.

Towards the end of 2015 I focused more on my diet.  Once I did that, the results came quickly.

Would I recommend Volume 2?  ABSOLUTELY.

Would I recommend Volume 2 over Volume 1?  ABSOLUTELY.  The workouts aren’t that much longer, and if you’re already willing to put in the time why not go the extra mile.  With that said, I have to admit that the hardest workout so far comes from Volume 1 (GameDay & Overtime).  If you can incorporate that into a rest day or stretch day, you’re doing really well.

Be warned, just like Volume 1, Volume 2 is hard on the body.  After 4 weeks you might want to switch to a less demanding workout for about a week and then get back to Volume 2 if you desire.

What’s next?  I can’t resist.  I’ve heard so much about Insanity Max:30.

Java 8 and GoDaddy SSL certificates

I recently ran into an issue where I was trying to integrate two applications over SSL.

I was getting this error (which was covered in one of my earlier blog posts): PKIX path building failed: unable to find valid certification path to requested target

Essentially, GoDaddy is phasing on SHA-1 certs and moving to SHA-2 certs.  Check this out for further information:


In my case we were running Java 8 u60, so we had to import gd_bundle-g2-g1.crt into cacerts by running:

%JAVA_HOME%\jre\lib\security>keytool –import –alias gd_bundle-g2-g1 –file gd_bundle-g2-g1.crt –keystore cacerts -trustcacerts

And as you probably know, the password is changeit

Spring Security: Supporting Multiple LDAP Directory Services


The application I was working on authenticated against Active Directory (AD).  However, I wanted each developer to have the ability to run the full-fledged application on their own developer machine, and running AD on a developer machine isn’t ideal. Hence, problem #1.


Thankfully, there are free LDAP servers available.  Apache Directory Studio and Active Directory Lightweight Directory Services (AD LDS) are just a few.

Approach A:

We first tried Apache Directory Studio but the application would not recognize the username.  Finally we determined that AD accepts the sAMAccountName attribute as the username, while most other LDAP servers simply use uid.  So problem #2 became, how do we support both?

Approach B:

It turns out what I really needed to do was create an LDAP search filter.  And I found a great how-to on the Atlasssian website of all places.

So the spring security configuration went from:

<bean id=”userSearch”
<constructor-arg index=”0″ value=”” />
<constructor-arg index=”1″ value=”(sAMAccountName={0})” />
<constructor-arg index=”2″ ref=”contextSource” />

to this:

<bean id=”userSearch”
<constructor-arg index=”0″ value=”” />
<constructor-arg index=”1″ value=”(|(uid={0})(sAMAccountName={0}))” />
<constructor-arg index=”2″ ref=”contextSource” />

Another problem:

I wish I could say that solved everything.  Unfortunately, Apache Directory Studio became non-responsive on multiple developer machines after a restart.

We were unable to get it up and running again so we switched to AD LDS.  This proved to be a better fit for us because Apache Directory Studio was required to run in the foreground.  With AD LDS we could run it in the background.  However, one downside of AD LDS is that you require a client tool, like ADSI Edit to configure it.  Also, there was 1 gotcha.  You need to add your newly created users to the ‘Reader’ role.  You do that by adding them to the ‘member’ attribute of the Reader role.

Spring Security: Migrating from 3.x to 4.x

So I started out migrating the Spring components of my web application by updating Maven to pull the 4.x Spring releases.

I expected some changes with regards to Spring MVC, but I didn’t expect changes related to Spring Security.

The spring-security.xml started out as follows:

And the login.jsp had the standard fields and action:

<form name='loginForm' action="<c:url value='/j_spring_security_check' />" method='POST'>




<td><input type='text' name='j_username'></td>




<td><input type='password' name='j_password' /></td>



<td colspan='2'><input name="submit" type="submit" value="submit" /></td>




The problem started when I had the application entirely running on Spring 4.x and I tried logging in without success.

Nothing made sense.  I examined the logs which reported “Access is denied” and “anonymousUser”.  This seemed odd because the http posts seemed fine.

I tried modifying the spring-security.xml many times without success.  Then I tried to move the security configuration from xml to Java based.  Essentially, I introduced a SecurityConfig class (with @EnableWebSecurity annotation) but that didn’t work either.

Finally, I went back to the xml based configuration and added j_spring_security_check/j_username/j_password.  This solved the problem.  It still doesn’t make sense to my why I had to do that.

Here’s what the spring-security.xml ended up looking like:

<sec:http use-expressions=”true” auto-config=”true”>

<sec:csrf disabled=”true”></sec:csrf>

<sec:intercept-url pattern=”/css/*” access=”permitAll”/>

<sec:intercept-url pattern=”/images/*” access=”permitAll”/>

<sec:intercept-url pattern=”/jsp/login.jsp” access=”permitAll”/>

<sec:intercept-url pattern=”/**” access=”isAuthenticated()” />

<sec:form-login login-page=”/jsp/login.jsp” login-processing-url=”/j_spring_security_check” username-parameter=”j_username” password-parameter=”j_password” default-target-url=”/index.html” authentication-failure-url=”/jsp/login.jsp?login_error=1″ always-use-default-target=”true”/>

<sec:logout logout-url=”/j_spring_security_logout” invalidate-session=”true” logout-success-url=”/jsp/login.jsp?loggedout=true” />