GSoC’ 24 CircuitVerse | Week 1 Report
Google Summer of Code 2024 Coding period start on 27th May.
You can see my Community Bonding Period Experience Blog: here
Week 1 (27 May — 2 June)
I am really excited to start my contributions to CircuitVerse. Since the proposed UI hasn’t been reviewed yet, I consulted with Org admin Aboobacker MK and started my task: ‘Improve SSO Integration’.”
Single sign-on (SSO) is an identification method that enables users to log in to multiple applications and websites with one set of credentials. SSO streamlines the authentication process for users.
There are a lot of standards and protocols that provide SSO and some of the famous ones are
- Security Assertion Markup Language (SAML)
- Open Authorization (OAuth)
- Open ID Connect (OIDC)
First, I started SSO integration from the official OKTa Documentation (Here), which uses the below gems,
- omniauth-oktaoauth — our OAuth strategy gem for Okta
- activerecord-session_store to handle our session
- figaro for managing our application YAML files to hold our environment variables and finally
- omniauth-rails_csrf_protection to protect us from that CRSF vulnerability mentioned prior
However, I was receiving an unexplained problem, which I tried to fix but couldn’t. After speaking with Aboobacker, I was therefore recommended not to use a specific Identity Provider (IDP) gem. It makes sense that I was instructed to utilize gems that are unrelated to any particular IDP instead.
In addition, I’m having trouble obtaining my Microsoft Azure credentials. I thus began SAML-based SSO for OKTA, but all of the available resources relied on Rails 5 and lower .
Conclusion
Despite not being able to deliver any PRs, I gained a lot of knowledge this week regarding SSO integration. I’ve decided to post the most recent materials for Ruby on Rails SSO integration with Okta. Keep an eye out for my upcoming blogs, where I promise to share some incredible information.
Thank you for reading! 😇