WSO2 Identity Server ~ The Inside Story
How I ended up working in middleware, and what it was like back then.
WSO2 was my second job since graduation. As anyone who is excited of his first day at work, I walked into this amazing, yet quite simple office building in Flower road, right opposite to the Ladies’ college. I knew nothing yet what I had to do — and thrown into a bunch of people who were developing a product called ‘WSO2 Identity Solution’.
WSO2 was nothing big like it is today. If I am not mistaken — we had no more than 30 engineers.
It was 1st of November 2007 — the entire Identity Solution team was busy working for its 1.0.0 release. Oh — yes.. I’ve been there since 1.0.0 release! and I am the only one yet remains in the team till its 5.0.0 release, which was in June 2014. This qualifies me enough to write this blog post. I’ve been with the team all the way through-out — all the way with sweet gains and bitter pains.
We had only three people actively working on the Identity Solution product in 2007. Do not count me yet — I just joined. It was Ruchith, Dimuthu and Dumindu. Nandana was there too, but he was mostly working on the Apache Rampart project.
Identity Solution 1.0.0 was released in December, 2007.
WSO2 Identity Solution 1.0.0 Released!http://blog.facilelogin.com/2008/12/wso2-identity-solution-10-released.html
I still remember, Dimuthu was arguing with Ruchith — ‘Are you sure we want to release this now?’. Dimuthu was an amazing character in the Identity Solution team — and since then we are extremely good friends. After some years she went on maternity leave and came back — I wrote the following email to the team list (email group), which is a clear reflection of who Dimuthu was :-). She is now a Director at WSO2 and also leading the WSO2 App Factory.
The ring tone heard for a while with no one to pick — once again I hear from my next desk…
The humming came around tea — comes once again and we know it’s tea….
Sound of a ‘punch’ on the desk, hear we again — she has fixed an issue..
She is back — and she is a mother now — of a wonderful kid…
She was a starting member of Axis2 and a key contributor to Rampart, WSO2 Carbon and Identity Server…
More than anything else she is the ‘Mother of User Manager’..
It’s my utmost pleasure to welcome back DimuthuL — after the maternity leave..
(29th November, 2010)
Ruchith was the key architect behind the Identity Solution and also the first product lead. Interestingly, he is also the very first WSO2 employee. Most of the Apache Rampart code is written by Ruchith. WSO2 had a great foundation on SOAP — and was actively involved in Apache Axis2 development. If someone is new to Rampart, it is the Axis2 module for SOAP security.
By December 2007 we only had very few products: Web Services Application Server (WSAS), Enterprise Service Bus (ESB), Data Services Solution (later became Data Services Server), Registry (later became Governance Registry) and the Identity Solution (later became Identity Server).
Identity Solution 1.0.0 only had the support for Information Card (InfoCard). Information Card is an open standard, mostly pushed by Microsoft, lead by Kim Cameron. Since WSO2 had a very strong foundation on WS-Security and WS-Trust, implementing the Information Card specification was quite straightforward. We were among the very few Java implementations that had support for Information Card by that time. We also actively participated in most of the interop events. On my first day at WSO2 I didn’t meet Ruchith, he was in USA participating in an Information Card interop event. Interop events definitely helped us to regulate the product in the right direction and validate our implementation. By the way, there was a popular joke at that time — an interop event is a place where all the other vendors test with Microsoft and fix anything that does not work with them :-).
In this article written by Dimuthu, explains how to add Information Card support for Java EE web applications: http://wso2.com/library/2994/
Identity Solution 1.0.0 was an Information Card provider. In addition to the product release we also released a set of Information Card relying party components along with the product. One was a Java EE servlet filter and the other one was an Apache module. Dumindu was the one who developed the Apache module — he was the C guy in the Identity Solution team.
How to setup an Information Card relying party with Apache:http://blog.facilelogin.com/2008/07/building-deploying-modcspace-on-windows.html
It was the era lot of changes started to happen in the field of Internet identity. Kim Cameron, the chief Identity Architect of Microsoft was one of the pioneers who lead the effort. He started building the famous Seven Laws of Identity with the community contribution. I was passionate about Kim’s writings and he was a hero for me. Later when I got an opportunity to visit Microsoft in April 2008, with Ruchith to participate in an Information Card design event — I was hoping — I would be able to meet Kim — but unfortunately he didn’t come for the event. Later — after many years — I met Kim several times and got the opportunity exchange few ideas. Arguably Kim is known as the father of the modern Internet Identity.
OpenID, in 2005 — followed the footsteps of SAML — and started to challenge Information Card, which was the most emerging standard by then and there was a lot of buzz around it. It was initiated by the founder of LiveJournal — Brad Fitzpatrick. The basic principle behind both OpenID and SAML, is the same. Both can be used to facilitate web single sign on and cross-domain identity federation. OpenID was not competing with Information Card, even though most got confused, when to use what.
It was my first task, to add OpenID support for WSO2 Identity Solution. It took almost 3+ months and shipped with Identity Solution 1.5.0 in April 2008 — just before the April holidays. In addition to OpenID 1.1 and 2.0 we also added OpenID InfoCard support. OpenID InfoCard specification talks about how to send OpenID claims in an Information Card. By the way, IS 1.5.0 was the first release which I acted as the release manager. For both IS 1.0.0 and 1.5.0 Chanaka (Jayasena) did the complete UI theming.
Information Cards vs OpenID Information Cards:http://blog.facilelogin.com/2008/01/infocards-vs-openid-infocards.html
Both IS 1.0.0 and 1.5.0 used struts to build it’s web interface. Most of the WSO2 products had got rid of struts by then — IS was the only remaining product. There was a rumor — it was because of Ruchith, Identity Solution was able to still go ahead with struts :-).
There was a discussion going on at that time to build a common framework to build all WSO2 products. With that, ESB won’t have its own web interface, App Server won’t have its own web interface — all the products will share the same web interface — same look and feel and the same object model. It was in early 2008 — we had the WSO2 Carbon kickoff meeting at the Trans Asia hotel (now Cinnamon Lake Side), Colombo. Both Ruchith and me were there representing the Identity Solution team. If I remember correctly I was the only one at that meeting who didn’t speak a single word :-).
WSO2 Carbon later became an award winning framework to build servers — based on OSGi.
Just after the IS 1.5.0 release, we had a client interested in implementing OpenID support with it. This was my first client engagement as well as the very first client for the Identity Solution. Ruchith and I had to fly to London. We were informed about the client engagement a month or two before — but none of us was keen to apply for VISA. At that time it took minimum three weeks to get UK VISA. But it was just a week or two before we applied. Both of us were given an earful by our CTO, Paul. For everyone’s surprise — both of us got VISA just within 3 days :-). Even today we do not know how that magic happened!
It was my first trip out of the country and I was lucky to be accompanied with Ruchith, who was an amazing guide! We met Paul (our CTO) in London and all three of us went to the client. Just before we entered into the client premise, Paul turned to us — first to Ruchith — ‘You are the security expert’ — then to me — ‘You are the OpenID expert’. We went in.
After finishing our stuff with our first Identity Solution client — both Ruchith and me flew to Seattle to participate in a technical design meeting at Microsoft around the future of Information Card. Then again we had to return back to London to finish some more stuff with our client. Interestingly, in our return trip to London — only at the hotel reception at the Holiday Inn, we found there were no hotel bookings for us. We got Udeshika (who is our Vice President of Administration now) on phone and she settled everything for us.
Few weeks after returning back to Colombo from 3 weeks long UK/USA trip — I had to get ready for the first ever Identity Solution webinar. Unlike nowadays we did not have webinars frequently, then. It was on ‘Understanding OpenID’ — I was over-joyed by the response!
Ruchith left the company in July, 2008 for his higher-studies. He joined University of Purdue and after completing his Ph.D last year, now works for Amazon. The photo above was taken at Ruchith’s farewell — from left to right — Dimuthu, Dumindu, Ruchith, Nandana and me. The image on Dumindu’s shirt is an Information Card.
Never they leave.. just checking out.. :http://blog.facilelogin.com/2008/07/never-they-leave-just-checking-out.html
Everyone started to be fascinated about Carbon and OSGi. The plan was to build WSO2 WSAS and the ESB on top of WSO2 Carbon, first. Focus on the Identity Solution was diluted a bit during this time. Security was a key part in the Carbon core and the entire Identity Solution team had to work on the migration — to make the User Manager component OSGi compliant and make it a part of the Carbon platform.
WSO2 User Manager started as a WSO2 Commons project and it had its own release cycle and its own product page. It was just a library and included in all WSO2 products. User Manager knows how to connect you to an LDAP, Active Directory or to a JDBC based user store. Most of the User Manager code by that time was written by Dimuthu — she was called User Manager Manager :-)
Nandana was the Rampart guy. He was actively contributing to the Apache Rampart and Rahas. During the initial Carbon release Nandana played a key role in bringing them into the Carbon platform.
After the initial release of WSO2 WSAS and ESB on top of Carbon — next came the Identity Solution, Registry and the Mashup Server. It was almost a complete re-write. After Ruchith left the company for higher-studies I was appointed as the Product Manager of Identity Solution and had to lead the migration effort to Carbon platform. It was easy by then, since the complete pain was taken by ESB and WSAS teams — we knew who to meet when hit with an issue.
During the same period, in April 2009, Thilina joined Identity Solution team. In the above photo — from left to right Thilina, Nandana and me.
Thilina’s addition to the team reduced our load on migration. His first contribution was to implement SAML 2.0 token profile support for Apache Rampart. Rampart was a key component in Identity Solution and one of our customers was waiting for the next Identity Solution, requested SAML 2.0 token profile support. In addition to that Thilina also implemented XMPP based authentication for OpenID logins. XACML 2.0 support was also another customer requirement. For anyone new to XACML, XACML is the de facto standard for policy based access control. I implemented that on top of Sun XACML implementation (later we forked Sun XACML as WSO2 Balana and implemented XACML 3.0 on top of it).
After IS 1.5.0 — it took more than an year to do the next IS release — which was IS 2.0.0.
Sumedha, who was leading the Data Services Solution, by that time (now the Director of API Architecture) came up with a suggestion to rename the product to Data Services Server. We followed the same approach and in July 2009 released the Identity Server 2.0.0. IS 2.0.0 is the very first version of the Identity Server built on top of WSO2 Carbon platform.
Even though we added XACML support for IS 2.0.0 — it was at very basic level. There was no editor — you simply need to write the policy by hand. The first comment from one of customers was : ‘Nice — but you got to have a PhD in XACML to write policies with your Identity Server’. He was not kidding — we took it dead seriously. Later when Asela joined the IS team — he worked on developing one of the best XACML policy editors for the Identity Server.
Couple of months after the IS 2.0.0 release, in September 2009, Nandana left the company to pursue higher-studies. He joined Universidad Politécnica de Madrid as a Ph.D student. Following photo was taken during Nandana’s farewell.
Soon after Nandana left, Thilina stepped up and filled the vacuum created by the absence of Nandana. By then we had Dimuthu, Thilina and me in the Identity Server team. In October 2009, we released Identity Server 2.0.1. In addition to the bug fixes we also added WS-Federation passive profile support for IS 2.0.1. Just after a month from the 2.0.1 release, I did a demo and a talk on its support for WS-Federation passive profile at the ApacheCon 2009 — in November. It was my first ApacheCon and also its the 10th anniversary of the ApacheCon.
I met Nandana who left WSO2 in September, at the ApacheCon.
We didn’t add much to the Identity Server 2.0.2 release done in November 2009 and the Identity Server 2.0.3 release in February 2010. Mostly those were bug fix releases. Focus on Identity Server new features faded down a bit during this period mostly due to the increased interest on cloud.
Around mid 2009, during a company dinner with the board at the Hilton Hotel Colombo, I met Paul. Paul mentioned company’s interest to move into the cloud and had identified to offer the WSO2 Governance Registry and the WSO2 Identity Server as cloud services to get started with.
Governance as a Service (GaaS) was the first ever WSO2 cloud offering. It was in January, 2010. Next to follow was Identity as a Service (IDaaS) in February, 2010. Thilina played a major role in adding muti-tenancy support for Identity Server. OpenID, Information Card, XACML all were made available as cloud services. In 2011, we were awarded with theKuppingerCole European Identity Award in cloud provider offerings category.
Still the Identity Server team was just 3 members: Dimuthu, Thilina and me. Most of the time Dimuthu focused more on the user management component. It was the time we got few new faces. Amila (Jayasekara) joined the Identity Server team in March 2010, Asela in April and Hasini in September. We were six then. Around the same time Dimithu went on maternity leave — Amila and Hasini started looking into what Dimuthu did. We were back to 5 members.
Interestingly Asela joined WSO2 as a QA engineer and straightway started testing Identity Server. He is an amazing guy — and also a batch mate of Thilina from the University of Moratuwa. After few months of testing Identity Server and reporting bugs — we felt it was enough him having in QA and took him directly to the Identity Server development team. Just as a twist of fate, once Asela joined the development team he had to fix the bugs reported by himself as a QA engineer :-)
Once Hasini joined the team, Amila shifted from focusing on user manager to Rampart and WSS4J improvements. He worked on upgrading Rampart to work with WSS4J 1.6.
Once done with the IDaaS deployment — we again started worrying about adding more ingredients into the Identity Server product. Initially GaaS had its own login and IDaaS had its own . There were also more cloud offerings to follow — ESB, App Server, Data Service Server and many more. One critical requirement raised, due to the need to login multiple times for each cloud service was, the support for single sign on (SSO) between all WSO2 cloud services. We already had support for OpenID — but then again we picked SAML over OpenID to cater our need there.
SAML was mostly used to facilitate web single sign on. It can be just within the same domain or between domains. SAML v2.0 — in 2005 — was built on the success of SAML 1.1 and other similar single sign on standards. It unified the building blocks of federated identity in SAML v1.1 with the inputs from Shibboleth initiative and the Liberty Alliance’s Identity Federation Framework. It was a very critical step towards the full convergence for federated identity standards
Someone had to implement SAML and add it to the Identity Server. Naturally it was Thilina, who already had experience working with SAML — while implementing SAML 2.0 token profile support for Apache Rampart. Thilina implemented SAML 2.0 Web SSO and SLO profiles for Identity Server.
OAuth was another area of focus for us. OAuth 1.0 was the first step towards the standardization of identity delegation. I started adding OAuth 1.0 2-legged support for Identity Server — and in May, 2010 — when we releasedthe Identity Server 3.0.0 — both the SAML 2.0 and OAuth 1.0 features were included.
2-legged OAuth with OAuth 1.0 and OAuth 2.0:http://blog.facilelogin.com/2011/12/2-legged-oauth-with-oauth-10-and-20.html
Asela played the release manager role of the Identity Server 3.0.1 — releasedin September, 2010 — as a bug fix release.
Even though we had support for XACML in Identity Server we were left behind with two issues. We didn’t have a proper XACML editor and also we didn’t have the support for XACML 3.0. We implemented XACML support on top of Sun XACML and by that time it was a dead project and only had 2.0 support. Asela was our choice to work on this. His first serious task, after joining the Identity Server team was to implement a XACML policy wizard. It was not easy. We did not want to build just another editor. After some iterations Asela came up with one of the best policy editors out there for XACML. We included it for the first time in Identity Server 3.2.0, which wasreleased in June, 2011.
IS 3.2.0 also had another key feature addition apart from the XACML policy editor. So far we shipped all WSO2 products with an H2 based user store. It was Amila who integrated Apache Directory Server LDAP with the Identity Server and all the other WSO2 products. Later, except Identity Server all the rest went back to use the same H2 based user store. In addition to that, Amila also integrated Kerberos KDC support from Apache DS with the Identity Server. Identity Server 3.2.0 could act as a Kerberos key distribution center.
While the team was working for the next Identity Server release, we had an interesting event in Sri Lanka : National Best Quality ICT Awards 2011. WSO2 participated there for the first time in 2010 and WSO2 ESB won the overall gold. 2011 was the first for WSO2 Identity Server. Along with the Identity Server, WSO2 Governance Registry, WSO2 Carbon and WSO2 Application Server were submitted for the awards, under different categories. Identity Server was submitted under the ‘Research and Development’ category. All three products were selected for the first round. Senaka (Gov Registry), Hiranya (Application Server), Sameera (Carbon) and I (Identity Server) presented each product before the judge panel. We went to the second round — and to the finals. We knew nothing about the awards till those were announced at the awards ceremony on 8th October. I missed the awards night — was with a customer in New Jersey, USA. It was Paul who passed me the message first, over chat — that Identity Server has won a Gold. I was with Amila and Asanka — we were thrilled by the news. Governance Registry won a Silver award, Carbon won a Merit award and Application Server won the overall Gold.
In the following photo Thilina (third from the left) is carrying the award for the WSO2 Identity Server.
In November 2011, we did the Identity Server 3.2.2 release. It had more improvements to the current feature set. One key improvement was to support OAuth 1.0 3-legged OAuth.
In December 2011 Identity Server 3.2.3 was released. Hasini was the release manager. One of the key improvements we did for IS 3.2.3 was to introduce a Thrift interface for the XACML PDP engine. Till then it was only SOAP and later we found that Thrift was 16 times faster than just SOAP over HTTP. IS 3.2.3 was a huge success. Even today, the largest deployment of the Identity Server is based on IS 3.2.3. One of our clients runs Identity Server over a 4 million+ user base in Saudi Arabia, as an OpenID Provider.
The following photo was taken at the ELM office Saudi Arabia, who implemented the OpenID support with WSO2 Identity Server 3.2.3. Later they also did a case study with us.
Since IS 3.2.3 — it took almost an year to do the next release : Identity Server 4.0.0 . During this time we got two new faces to the team — Suresh and Johann. I knew Suresh well — since he did the internship at WSO2 and I also supervised his final year University project. Suresh and his team implemented OpenID based authentication for SOAP based services with WS-Security. Also they implemented some of the WS-Federation features to Apache Rampart. Johann was totally new to the WSO2 Identity Server team.
IS 4.0.0 had major improvements and feature additions. Thilina developed OAuth 2.0 support for IS 4.0.0 and also it became a key part of the WSO2 API Manager’s success. It was the time WSO2 made its entry into the API Management market. Both Sumedha and I were initially involved in building it and later Sumedha lead it alone. I was mostly there since security is a key part of it. Thilina and Johann both got involved in the initial API Manager implementation. Johann mostly worked on integrating API Manager with WSO2 Business Activity Monitor for statistics.
In July 2012, both Thilin and Amila left the company to pursue higher-studies. Currently Thilina is a Ph.D student at the Colorado State University and Amila doing his Ph.D at the Indiana University Bloomington.
Asela was still busy with XACML. He is one of the top experts on it and writes the blog http://xacmlinfo.org/. It was high-time that we wanted to bring XACML 3.0 support to IS. Sun XACML project was dead silent and we made the decision to fork and add XACML 3.0 support on top of it. We called it WSO2 Balana. Interestingly Srinath came up with that name. Balana is a famous checkpoint closer to Kandy, Sri Lanka, which protected the hill country from British invasion. Asela himself did almost all the development to add XACML 3.0 support for Balana.
Another feature which we added to IS 4.0.0 was SCIM. One of the key standards for Identity Provisioning by that time was SPML. But it was too complex, bulky and biased to SOAP. People started to walk away from SPML. In parallel to the criticisms against SPML — another standard known as SCIM (Simple Could Identity Management — later it was changed to System for Cross-domain Identity Management) started to emerge. This was around mid 2010 — and initiated by Salesforce, Ping Identity, Google and others. WSO2 joined the effort sometime in early 2011.
SCIM is purely RESTful. The initial version supported both JSON and XML. SCIM introduced a REST API for provisioning and also a core schema (which also can be extended) for provisioning objects. SCIM 1.1 was finalized in 2012 — and then it was donated to the IETF. Once in IETF, it had to change the definition of SCIM to System for Cross-domain Identity Management and it’s no more supporting XML — only JSON.
Hasini was our in-house SCIM expert. Not only she just implemented the SCIM support for Identity Server, she was also a SCIM design team committee member. SCIM was developed as a WSO2 Commons project — under the name WSO2 Charon. The name was suggested by Charith. The Charon 1.0.0 was released in March, 2012 just in time for the very 1st SCIMinterop in Paris. Hasini represented WSO2 at the interop event.
One limitation we had in our SAML Web SSO implementation was that — we did not support attributes. It was Suresh who implemented SAML Attribute Profile support for the Identity Server.
We also did more improvements to our XACML implementation, targeting the 4.0.0 release. Johann was the one who brought in WS-XACML support to the Identity Server. In addition to the SOAP/HTTP, Thrift interfaces, we also added an WS-XACML interface to our XACML PDP. This is one of the standard ways to communicate between a XACML PEP and a PDP. WS-XACML is quite heavy and has huge impact on the performance. If not for a strong customer requirement — we might not have added WS-XACML to the Identity Server.
We also further improved our Active Directory user store manager. It was just read-only and Suresh implemented read/write capabilities and also later added the support for Active Directory Lightweight Directory Services (AD LDS).
Another feature we added to IS 4.0.0 was the Integrated Windows Authentication (IWA) support. With this, if you are already logged into your Windows domain, you need not to re-login to Identity Server. This was developed by Pulasthi — who was an intern then. After the graduation Pulasthi joined WSO2 in 2014 and joined the Identity Server team. The IWA support in IS 4.0.0 was just limited to the Identity Server’s management console login. This was not available for SAML/OpenID based logins. Identity Server 5.0.0 later added that support.
With all these new features — Identity Server 4.0.0 was released in November 2012.
After the Identity Server 4.0.0 release we found an interesting client who was developing a mobile navigation app for a user base more than 600 millions. They were interested in using Identity Server. Suresh, Tharindu and I were there onsite for a week and came up with a design. Due to the large number of users — we all agreed to go ahead with a user store based on Apache Cassandra. In fact client suggested that and Tharindu who was an expert on Big Data was with us to confirm it. We implemented a Cassandra based user store manager and plugged in Cassandra as a user store to the Identity Server. With this feature and some minor improvements Identity Server 4.1.0 was released in February, 2013. We also added the support for multiple user stores at a very primary level to IS 4.1.0.
Identity Server team by now was five members: Hasini, Asela, Johann, Suresh and me. Everyone lifted themselves to fix the gap created by the absence of Thilina and Amila. Darshana and Pushpalanka joined the Identity Server team a couple of months after the IS 4.1.0 release. I knew both of them even before joining WSO2. The final year University project Darshana did was supervised by me. It was an interesting one — to build a XACML policy engine based on a RDBMS. Pushapalnka was an intern at WSO2 and during her internship period she did some interesting work around XACML.
The immediate next release after the IS 4.1.0 was 4.5.0. The main focus of IS 4.5.0 was to enhance the user-friendliness of its user management UI and strengthen its multiple user store support. In addition to that Suresh worked on adding OpenID Connect core support and Johann worked on implementing SAML 2.0 grant type for OAuth 2.0 profile.
Prior to IS 4.5.0 — and after IS 4.1.0 — the entire Identity Server team had to work hard on a customer project. We developed most of the features that went with IS 4.5.0 and bundled them to IS 4.2.0 (this version was never released). The entire team was so desperate to make the project a success — but — due to some stuff that are not under our control — we lost the project. This was the time Dulanja, Ishara, Venura and Dinuka joined the Identity Server team. Venura later left WSO2 to join a company in Singapore and Dinuka left to USA with his wife who got admission to a University for higher-studies. Dulanja and Ishara are still with WSO2, later played a key role in the Identity Server 5.0 release.
In the following photo Johann, Asela and I were at a Walmart store, on our way back from the above client, after successfully completing the deployment. Some customers we win — some we loose — that’s the life.
Hasini left the company in June 2013 for higher studies. It was few month prior to IS 4.5.0 release. She joined the University of Purdue. Following photo was taken at her farewell at the JAIC Hilton hotel Colombo.
Darshana was the release manager for the Identity Server 4.5.0 and wasreleased in August 2013. Pushpalanka also played a key role in this release by developing the user store management component — that let you add and configure multiple user stores from the Identity Server’s management console.
WSO2 Identity Server 4.6.0 was released few months after 4.5.0, in December 2013. It had only one feature, Identity Provider initiated SAML SSO support. Johann played the release manager role for this release.
The 4.6.0 release was the end of one generation of the Identity Server. Nobody knew that till we released Identity Server 5.0.0 in May 2014. We took a completely new approach to IS 5.0.0. Till then we were developing just isolated features. We changed that approach and started to build user experiences — instead of features. You need to develop features to build user experiences — but the angle you look into that is completely different. When you look into something from a different angle — what you see is different too.
Building Identity Server 5.0.0 was not just a walk-in-the-park. It went through several iterations. We had to throw-away some stuff when we found better ways of doing that. In addition to the identity broker support with identity token mediation and transformation, IS 5.0.0 also introduced a new user interface for end users. Prior to that, both the administrators and end users, had to use the same management console, and the functions available were filtered out by the role of the user. With IS 5.0.0 we built a whole new dashboard with jaggery — which is a home-grown framework to write webapps and HTTP-focused web services for all aspects of the application: front-end, communication, server-side logic and persistence in pure java-script. This was initiated by Venura — who started developing the dahsboard in jsp — and then after couple of months — Venura moved to the WSO2 App Manager product, since it required some security expertise. After Venura left the team, Ishara took over — and we changed everything from jsp to jaggery. Venura left the company to Singapore after several months working in the App Manager team.
WSO2 Identity Server 5.0.0 release was a huge success. Most of the Identity Server deployments are now on IS 5.0.0 than any of its previous releases. The best thing about IS 5.0.0 is — it opened up a whole new world (being able to act as an identity broker) — and 5.0.0 release is the first step towards that direction — but an immensely sound foundation.
During the IS 5.0.0 release we got three new faces — Thanuja, Isura and Prasad. Even though they had very little experience at WSO2 by then, their contribution to the 5.0.0 release was fabulous.
Following photo was taken on the day we released Identity Server 5.0.0. From left, Suneth (who is from the QA team — and worked on Identity Server testing with Pavithra and Ushani. Pavithra was the QA lead for IS testing for so many releases), Isura, Ishara, Johann, me, Darshana, Dulanja, Thanuja and Prasad. Suresh, Pushpalanka and Chamath who also contributed to 5.0.0 release a lot, missed the shot.
On the same day Identity Server 5.0.0 was released, Johann was made the product manager. I was planning to move into the WSO2 Mountain View, USA office and Johann was carefully groomed into this position, for several months. Even-though I left the Identity Server team officially in May — I worked very closely with the team till I left the country to USA, on 14th January, 2015.
Following token was given to me by the team on my last day at the WSO2 Colombo office. It’s a representation of all great memories I had with the Identity Server team, since its inception.
Originally published at blog.facilelogin.com on June 7, 2015.