You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I implemented oidc/oauth2 during the last few weeks and spend a lot of time just reading through RFC specifications and implementing them. Unfortunately I underestimated the amount of time this would take and how tiring this work is.
SigAuth was originally started to bring free fine-grained-access control (FGA) to the brought free mass and I added authenticating just because it would be nice to have not knowing about the variety protocols, customizations and features required to deliver a truely useful IdP.
While this is still the end goal of the project I want to refocus on the problem that SigAuth originally wanted to solve and hope for the contributions of others to improve authentication and user management later on
As far as I know there is only one project that has a similar schema flexibility as SigAuth called Permify. It was recently acquired by FusionAuth but has a fundamental different approach on storing and serving the authorization data which is why I want to layout the key features which SigAuth aims to Improve in comparison to Permify
Permify only offers storage for data which is relevant for authentication
This results in situation where you have two databases. One maintained by Permify and one maintained by your application. They are either mirrored or lack some of the data.
SigAuth serves as your centralized database containing all the data of your project automatically picking which is relevant to resolve your access request and which is not.
You only interact with Permify through a static API Wrapper
SigAuth offers far more than a simple Api Wrapper library but allows you to query your data directly while including authorization parameters
TL:DR
SigAuth will be focused on only offering authorization services for the near future containing compatibility for external IdPs like FusionAuth, Clerk or Okta using OIDC. This is where SigAuth can solve real issues and not just create structures and solve problems that already have been solved or created.
SigAuth will still aim to become an all-in-one solution in the long term, but this won’t be part of a first full release.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I implemented oidc/oauth2 during the last few weeks and spend a lot of time just reading through RFC specifications and implementing them. Unfortunately I underestimated the amount of time this would take and how tiring this work is.
SigAuth was originally started to bring free fine-grained-access control (FGA) to the brought free mass and I added authenticating just because it would be nice to have not knowing about the variety protocols, customizations and features required to deliver a truely useful IdP.
While this is still the end goal of the project I want to refocus on the problem that SigAuth originally wanted to solve and hope for the contributions of others to improve authentication and user management later on
As far as I know there is only one project that has a similar schema flexibility as SigAuth called Permify. It was recently acquired by FusionAuth but has a fundamental different approach on storing and serving the authorization data which is why I want to layout the key features which SigAuth aims to Improve in comparison to Permify
TL:DR
SigAuth will be focused on only offering authorization services for the near future containing compatibility for external IdPs like FusionAuth, Clerk or Okta using OIDC. This is where SigAuth can solve real issues and not just create structures and solve problems that already have been solved or created.
SigAuth will still aim to become an all-in-one solution in the long term, but this won’t be part of a first full release.
Beta Was this translation helpful? Give feedback.
All reactions