remix-saml-authentication VS starchart

This week started with me pulling from the Offical SAMLIFY docs and the Remix SAML example. I got the authentication process to work but I did not add signature requirements or validation of signatures, and I was also importing the sp and idp objects and exposing them in every file where there was supposed to be some SAMLIFY logic, and I also fetched the idp xml metadata from the endpoint the simple saml php container exposes it on, I changed this in a consequent commit so that we have the file locally and read it using fs, all of this is kind of subject to change and that is the essence of the problem.

Another starting point is right there, Samlify docs. Further than that David found a perfect example for our tech stack where someone has made an example implementation of SAMLIFY with REMIX here. So taking a look at these things would be a start.

This week was a big one for the authentication part of starchart, or it should have been.

The past week, I have been working on creating the record creation page UI. This involves creating a form component that will be reused on this and the edit record page. A record has a name, type (A/AAAA/CNAME/TXT), value, and some other fields such as ports, course, and description, which provide context to the use of this record. Originally, this page was called a domain creation page as mentioned in the issue. However, after some discussion on the PR, it was decided that it should really be called the record creation page

What I have come to realized as I work with the repo is my lack of understanding of what I'm even doing. I write code base on the research I've done, but it seems that I don't try to understand them, and just look at the code and implement it based on what I need. I realized that this type of thinking is flawed and can never work.

This week, I'm tweaking column names and adding CRUD functions to the Startchart project.

This week I intend on implementing functionality for sending email notifications when a domain becomes active or errors using BullMQ workers queues. Also, working with BullMQ may prove challenging, but I want to give it a shot, as I would gain valuable experience. Another goal is to update the Dependabot configuration to avoid non-LTS node version updates. Lastly, since I am one of the Sheriffs this week, I intend to be highly available should any problems be addressed promptly.