WSO2

Mentors: Student: Isuranga Perera

<p>WS-Trust is a WS-* specification that provides extensions to the WS-Security specification. WS-Security provides the basic framework for message level security in web services. WS-Trust builds on that base to specify a framework for broker trust across different security domains. It specifically deals with the issuing, renewing, and validating of security tokens, as well as with ways to establish, assess the presence of, and broker trust relationships between participants in a secure message exchange. This project focuses on implementing the WS-Trust specification for the WSO2 Identity Server 6.0.0 by simply integrating with Apache CXF.</p>

Mentors: Student: Udeshika Sewwandi

<p>WSO2 Complex Event Processor(WSO2 CEP) is real-time and it has a quick response time in identifying patterns in incoming stream of events/large data feeds with minimum storage. WSO2 CEP is popular among community since it’s simple and easy to use as well as since it is free and open source. The core of WSO2 CEP is Siddhi which is a SQL-like query language that is used for complex queries. An Eclipse plugin for Siddhi is a valuable approach for the developer community since eclipse IDE is a widely used IDE among developers. Eclipse plugin for Siddhi will comprise syntax highlighting, auto completion, error reporting, running and debugging support for Siddhi based on Siddhi grammar using Xtext and Java.</p>

Mentors: Student: Vindula Jayawardana

<p>The proposal is on implementing the SCIM 2.0 compliance test suite which can be run on both the cloud and on premise by eliminating the limitations that can be seen in SCIM 1.1 compliance test suite. In the proposed test suite, it is expected to validate the supportability of a provided service provider, in terms of the SCIM 2.0 core specification and protocol specification.</p> <p>The test suite should be able to generate a detailed analysis view and comprehensive report upon providing the server’s SCIM endpoint. The report should include the test results indicating the coverage percentage of each specification and a detailed view of the results of each test including requests sent by the test suite, expected response and the server response along with the indication whether a particular test is passed or not.</p> <p>Apart from that the test suite should be run against WSO2 Identity Server to identify any gaps between the SCIM 2.0 specifications and Identity Server and provide improvements to the product.</p>

Mentors: Student: Abilashini Thiyagarajah

<p>OAuth 2.0 Dynamic Client Registration Management Protocol specification defines a set of rules to manage the OAuth 2.0 Dynamic Client Registration which is already supported by the WSO2 IS. OAuth 2.0 Dynamic Client Registration Protocol describes how a client dynamically registered in the authorization server. But there can be situations where client needs to modify the registered data or check the current registration data or delete the data from the authorization server. So OAuth 2.0 Dynamic Client Registration Management Protocol came up with methods to enable the above functionalities. The primary scope of this project is to implement the OAuth 2.0 Dynamic Client Registration Management Protocol in the WSO2 Identity Server.</p>

Mentors: Student: Nadun De Silva

<p>This project consists of two main parts of the automated generation of documentation for Siddhi Complex Event Processing Engine.</p> <ol> <li>a maven plugin for automated documentation generation for a single extension module or the siddhi core. The metadata annotated using the @Extension annotation are retrieved using the ClassIndex library which is already used by siddhi for indexing the annotated processor classes. Afterwards, documentation is generated using the metadata using a template engine.</li> <li>Creating an index of the Siddhi Extension Repositories.</li> <li>Adding and committing the <code>docs/</code> directory content and the <code>mkdocs.yml</code> file to Git. Pushing the changes in the <code>docs/</code> directory content and the <code>mkdocs.yml</code> file to <code>origin master</code>. Automatically deploying documentation in each new release of Siddhi.</li> </ol>