Articles on nilupul's Blog

Weekly blog post 22

n.manodya@gmail.com (nilupul) — Fri, 27 Oct 2023 05:45:15 +0000

What did you do this week?

This week, I worked on the developer documentation and opened a pull request for that. I also started working on the implementation of functional test cases and opened a draft pull request. Additionally, I started references for configuring the current project on the server.

What is coming up next?

Next week, I hope to work on the suggestions from the developer documentation and sort out all functional test cases for the developed project. I also hope to set up the project successfully on the remote server.

Did you get stuck anywhere?

View Blog Po

Weekly blog post 21

n.manodya@gmail.com (nilupul) — Sat, 21 Oct 2023 07:41:45 +0000

What did you do this week?

In the this week, I worked on minor improvements of the project based on the previous comments and opened pull requests (#2063, #2062). I also merged the current development branch into the GSoC project and opened the pull request (#2061).

What is coming up next?

Next week, I hope to finalize the developer documentation and sort all functional test cases for the developed project

Did you get stuck anywhere?

Weekly blog post 20

n.manodya@gmail.com (nilupul) — Mon, 16 Oct 2023 09:27:55 +0000

What did you do this week?

Last week, I dedicated time work on developer documentation along with the instruction of configuring IDPs like keycloak for the mscolab server and the comments of the last PR for implement mscolab for multiple Idps.

What is coming up next?

In the coming week, I hope to finalize the implementation of developer documentation by working on the comments on the developer documentation. also start working on the functional testcases.

Did you get stuck anywhere?

Weekly blog post 19

n.manodya@gmail.com (nilupul) — Mon, 09 Oct 2023 10:00:45 +0000

What did you do this week?

Last week, I dedicated time work on developer documentation along with the instruction of configuring IDPs like keycloak for the mscolab server.

What is coming up next?

In the coming week, I hope to finalize the implementation of developer documentation by working on the comments on the developer documentation.

Did you get stuck anywhere?

Weekly blog post 18

n.manodya@gmail.com (nilupul) — Sun, 01 Oct 2023 18:13:02 +0000

What did you do this week?

Last week, I dedicated time work on developer documentation along with the instruction of configuring IDPs like keycloak for the mscolab server. Also opened a PR with instructions to configure multipe IDPs for mscolab.

What is coming up next?

In the coming week, I hope to finalize the implementation of developer documentation by working on the comments on the developer documentation.

Did you get stuck anywhere?

Weekly blog post 17

n.manodya@gmail.com (nilupul) — Mon, 25 Sep 2023 15:14:12 +0000

What did you do this week?

Last week, I dedicated time to addressing the comments in PR #1974 and started work on developer documentation along with the instruction of configuring IDPs like keycloak for the mscolab server.

What is coming up next?

In the coming week, I hope to finalize the implementation of developer documentation along with the instruction of configuring IDPs like keycloak for the mscolab server. and worked to enable for multiple IdPs configurations for the mscolab server.

Did you get stuck anywhere?

Weekly blog post 16

n.manodya@gmail.com (nilupul) — Sun, 17 Sep 2023 08:58:24 +0000

What did you do this week?

This week, I dedicated time to addressing the comments in PR #1974 and worked on the implementation of SSL enablement for developers in mscolab server and opened PR.

What is coming up next?

In the coming week, I hope to work on the implementation of developer documentation along with the instruction of configuring IDPs like keycloak for the mscolab server.

Did you get stuck anywhere?

Weekly blog post 15

n.manodya@gmail.com (nilupul) — Mon, 11 Sep 2023 04:38:49 +0000

What did you do this week?

This week, I dedicated time to addressing the comments in PR #1974 and referred to boa documentation for additional fixes. I carefully reviewed the feedback, making necessary adjustments to improve the project. This process allowed me to gain a deeper understanding of the project requirements and implement more effective solutions based on the documentation's guidance.

What is coming up next?

I hope to further address the comments that I am currently working on, and afterward, I intend to proceed to address the task of transitioning from our currently self-created certificates, which are suitable for development purposes, to using certificates signed by a recognized authority. As part of this transition, we need to implement an option to "disable" unsigned certificates, or alternatively, set the default behavior to "always" use authority-signed certificates while allowing developers the option to disable this feature. This change is crucial because, with the default setting, a certificate can potentially be self-signed and lacks checks for its expiration or alignment with the authority's certificate chain.

Did you get stuck anywhere?

Weekly blog post 14

n.manodya@gmail.com (nilupul) — Sun, 03 Sep 2023 17:49:24 +0000

What did you do this week?

This week, my primary focus was addressing the necessary fixes in my previous PR. I also initiated a new PR related to these changes.

What is coming up next?

In the upcoming week, I hope to address the task of transitioning from our currently self-created certificates, which are suitable for development purposes, to using certificates signed by a recognized authority. As part of this transition, we need to implement an option to "disable" unsigned certificates, or alternatively, set the default behavior to "always" use authority-signed certificates while allowing developers the option to disable this feature. This change is crucial because, with the default setting, a certificate can potentially be self-signed and lacks checks for its expiration or alignment with the authority's certificate chain.

Did you get stuck anywhere?

Weekly blog post 13

n.manodya@gmail.com (nilupul) — Sun, 27 Aug 2023 07:48:26 +0000

What did you do this week?

During this week, I faced time constraints due to my ongoing 7th Semester examinations, which unfortunately limited my availability to contribute to the project.

What is coming up next?

I hope to continue the project from next week and focus on the fixes to-do in my last PR

Did you get stuck anywhere?

Weekly blog post 12

n.manodya@gmail.com (nilupul) — Fri, 18 Aug 2023 13:20:10 +0000

What did you do this week?

During this week, I faced time constraints due to my ongoing 7th Semester examinations, which unfortunately limited my availability to contribute to the project.

What is coming up next?

Due to my 7th-semester examination, I will not be actively available until the 27th of August.

Did you get stuck anywhere?

Weekly blog post 11

n.manodya@gmail.com (nilupul) — Fri, 11 Aug 2023 11:34:03 +0000

What did you do this week?

During this week, I faced time constraints due to my ongoing 7th Semester examinations, which unfortunately limited my availability to contribute to the project.

What is coming up next?

Due to my 7th-semester examination, I will not be actively available until the 27th of August.

Did you get stuck anywhere?

Weekly blog post 10

n.manodya@gmail.com (nilupul) — Sun, 06 Aug 2023 12:51:03 +0000

What did you do this week?

At the beginning of last week, I worked on the comments received for configuring IDP with the Mscolab server and worked until merging that PR. Due to my 7th-semester examinations starting on August 2nd, I was not active during the last few days of the week.

What is coming up next?

Due to my 7th-semester examination, I will not be actively available until the 27th of August.

Did you get stuck anywhere?

Weekly blog post 9

n.manodya@gmail.com (nilupul) — Mon, 31 Jul 2023 04:37:26 +0000

What did you do this week?

Last week, I worked on configuring IDP with the Mscolab server. During this time, I received some valuable feedback regarding implementing it for multiple IDPs and changing paths for certificates (crts). I worked on these improvements, and updated the Pull Request. Also the updates included automating some manual processes, such as creating crts and other metadata files.

What is coming up next?

Starting from the beginning of next week, my 7th-semester exams will commence (2nd Aug to 27th Aug). As a result, I will be a bit busy with exams and studies. However, I am determined to focus and commit time to address any feedback on the existing open PRs.

Did you get stuck anywhere?

Weekly blog post 8

n.manodya@gmail.com (nilupul) — Sun, 23 Jul 2023 17:39:28 +0000

What did you do this week?

I have been involved in configuring the MSS collaboration server and have opened a draft PR. Additionally, I have worked on configuring the MSColab server with an existing IDP keycloak. Here is the video how it works. Moreover, I have started referring to pytests for implementing the test cases.

What is coming up next?

Next week, my main focus will be on implementing the test cases. I am also hopeful about incorporating the necessary changes recommended by mentors. It's essential to ensure the project's success and meet the required standards.

Did you get stuck anywhere?

Weekly blog post 7

n.manodya@gmail.com (nilupul) — Sun, 16 Jul 2023 17:58:32 +0000

What did you do this week?

I have been involved in configuring the MSS collaboration server. Not only did I successfully configure the MSS collaboration server, but I also ensured the seamless integration with the QT client application. My efforts have contributed significantly to enhancing the server's collaborative capabilities and optimizing the overall user experience.

What is coming up next?

Regarding the configuration of the mscolab server, I need to perform additional file configurations. Once those are completed, my plan is to configure mscolab with the existing Identity Provider (IDP). This approach will enable smooth integration and enhance the server's collaborative functionalities.

Did you get stuck anywhere?

Weekly blog post 6

n.manodya@gmail.com (nilupul) — Sun, 09 Jul 2023 17:01:09 +0000

What did you do this week?

I have begun implementing the configuration of the MSS collaboration server. I worked on the UI improvements of QT application and I have submitted a pull request (PR) for the User Interface (UI) implementation of the QT application's IDP login feature. Additionally, I have opened another PR for the UI development of the PyQt web browser integration.

What is coming up next?

I have set aside time to enhance the authentication capabilities of the QT client application. The primary goal is to elevate the login functionality by integrating a browser component for the authentication process. Once the server confirms the authentication as successful, the client application will receive a distinctive token, allowing for secure communication.

Did you get stuck anywhere?

Weekly blog post 5

n.manodya@gmail.com (nilupul) — Mon, 03 Jul 2023 12:13:26 +0000

What did you do this week?

I have begun implementing the configuration of the MSS collaboration server. This includes setting up the server environment, ensuring its proper functionality, and making necessary adjustments to meet project requirements. Currently, I am actively working on this task.

What is coming up next?

I have planned to allocate my time to incorporate authentication into the QT client application. My objective is to improve the login functionality by integrating a browser element for the authentication procedure. Once the server verifies the authentication successfully, the client application will be granted a unique token, which will enable secure communication.

Did you get stuck anywhere?

i am getting stuck with writing test cases for the authentication SP and IDP. These test cases are running correctly on my local environment. When I tried to push them to GitHub, I encountered some failures because the server was not starting because of issue with file path in docker container. To resolve this issue, I believe I need to refer to the previously built codebase and utilize GitHub's Automated tests. I plan to address this matter later in the project, as outlined in the project proposal.

Weekly blog post 4

n.manodya@gmail.com (nilupul) — Sun, 25 Jun 2023 08:09:22 +0000

What did you do this week?

During this week, I focused on two main tasks. Firstly, I worked on splitting the localhost Identity Provider (IDP) and Service Provider (SP) into the main project of mslib. This involved organizing the code structure and ensuring seamless integration between the IDP and SP components.

In parallel, I dedicated time to developing test cases for the single sign-on process in a localhost environment. These test cases aimed to validate the functionality and security of the authentication flow between the IDP and SP. By meticulously designing and executing these tests, I aimed to ensure that the single sign-on process worked smoothly and reliably.

Additionally, I took the opportunity to familiarize myself with the codebase of mscolab, an associated project. This allowed me to gain insights into its structure and understand how to implement the single sign-on process with the localhost IDP.

What is coming up next?

In the upcoming week, my focus will be on implementing the configuration of the MSS collaboration server. This involves setting up the server environment, ensuring its proper functionality, and making any necessary adjustments to meet the project's requirements.

Additionally, I will be dedicating time to implementing authentication into the QT client application. This task involves enhancing the login functionality by integrating a browser component for the authentication process. Upon successful authentication by the server, the client application will receive a one-time token to establish secure communication.

Did you get stuck anywhere?

Weekly blog post 3

n.manodya@gmail.com (nilupul) — Sun, 18 Jun 2023 05:35:57 +0000

What did you do this week?

I primarily worked on setting up the Identity Provider (IdP) and Service Provider (SP) for the local MSS using pysaml2. Additionally, I addressed my mentor's feedback and learned how to maintain code quality and adhere to copyright policies specific to the MSS. Simultaneously, I encountered an issue with the pysaml2 library while configuring the local identity provider for our MSS. Consequently, I created a corresponding issue to propose and implement the necessary fixes for this particular functionality, enabling the seamless integration of our local identity provider into the MSS. Through this experience, I gained valuable insights into IdP/SP setup, code maintenance, and issue tracking in relation to the MSS.

What is coming up next?

Looking ahead, my immediate objective is to embark on the process of replicating the necessary steps for testing local identity provider. Simultaneously, in the upcoming week, I am eager to begin configuring the MSS collaboration server with our local identity provider. This crucial undertaking will greatly enhance the integration and functionality of our system. I am enthusiastic about these upcoming tasks and the progress we will make.

Did you get stuck anywhere?

Weekly blog post 2

n.manodya@gmail.com (nilupul) — Sun, 11 Jun 2023 05:10:01 +0000

What did you do this week?

I was opened draft PR for the setup SP and IDP for the Single sign-on process, which will used to integrate with MSS using pysaml2. This aimed to enhance the authentication system by implementing a secure and streamlined login experience. The draft PR contained detailed documentation, code improvements, and additional features to bolster the functionality and reliability of the Single sign-on setup. Same time i opened another PR by the correcting automated testing process of GSoC branch.

What is coming up next?

Based on the review of my draft PR, I have identified several areas that require corrections in the coming days. Simultaneously, I need to concentrate on configuring the MSS collaboration server. This involves installing a SAML service provider (SP) library on a local server and creating an SSL/TLS certificate and key for the server. Additionally, I need to configure the SP library with the metadata file and SSL/TLS certificate, utilizing a template for generating the data within the metadata file owned by the Service Provider. Finally, it is crucial to test the Single Sign-On (SSO) integration with the Identity Provider (IdP) to ensure seamless functionality.

Did you get stuck anywhere?

Weekly blog post 1

n.manodya@gmail.com (nilupul) — Mon, 05 Jun 2023 03:59:29 +0000

What did you do this week?

I developed our own service provider using pysaml2 authentication for the single sign-on process. This involved creating a robust system that allows users to authenticate and access multiple applications seamlessly. Additionally, I built our own identity provider using pysaml2, ensuring that we have complete control over user authentication and authorization. This IdP enables us to manage user identities and securely share user attributes with service providers. By developing both the service provider and identity provider, we have established a comprehensive and integrated solution for efficient and secure single sign-on functionality, providing a seamless user experience across our testing application.

What is coming up next?

Currently, I am encountering a dependency issue in the main project, which is impeding progress. However, I am actively working on resolving this issue, and once it is sorted, my plan is to create a pull request (PR) and discuss any necessary further improvements with my mentor for this task. Once the PR is submitted and the necessary discussions take place, my intention is to shift my focus towards the upcoming tasks scheduled for the upcoming weeks(Configure the MSS collaboration server for SSO). By addressing the dependency issue and collaborating with my mentor, I aim to ensure a smooth workflow and deliver high-quality results in a timely manner.

Did you get stuck anywhere?

Week 0 - 29th May 2023

n.manodya@gmail.com (nilupul) — Thu, 01 Jun 2023 03:51:23 +0000

Overview

During the community bonding period, which concluded this week, I focused on various activities. Firstly, I utilized this time to establish connections with fellow GSoC Contributors, fostering a sense of camaraderie within the community. Additionally, I dedicated myself to delving deeper into the Open-MSS codebases, enhancing my familiarity with their intricacies.

Work

During this period, I wholeheartedly dedicated my time and efforts to delving deeper into the codebases of Open-MSS. My primary objective was to enhance my familiarity with the intricate workings of the system. I delved into the various components, meticulously studying their structure and functionality. Through this immersive exploration, I aimed to gain comprehensive knowledge and develop a profound understanding of the inner workings of Open-MSS, laying a strong foundation for my future contributions.

The Week Ahead

In the upcoming week, I will focus on setting up our own Identity Provider (IdP) and conducting tests with an existing service provider (SP). This is essential to ensure the proper functioning of the Service Provider (SP) by having our IdP under our control. I will start by creating our IdP and performing tests with a Service Provider from another project. This process will provide valuable insights, allowing us to align our SP implementation with the other project. Based on the results, I will incorporate additional tests to enhance the system.