royalty-registry-solidity VS node-oidc-provider

https://opensea.io/collection/1989-sisters. As part of that project, I contributed to the open source Manifold royalty registry to patch an migration issue with OpenSea contracts that allowed for them to receive payments through Coinbase NFT: https://github.com/manifoldxyz/royalty-registry-solidity/pul....

Spending most of my time now back in Ruby/Rails, Docker, AWS and overseeing a small team of iOS developers and QA engineers based in eastern Europe (Ukraine as it happens). Also serving as our de facto product manager and designer and have handled all UI/UX/Iconography design in Figma. Extensive work with Plaid, multi-docker container deployments (AWS ECS/Fargate), subscription payments, etc. Fast learner and take pride in my craft.

Feel free to contact me. I'm happy to send work samples. Need to touch up my resume/portfolio/website but am posting here in the meantime. Thanks!

email: p dot osetinsky at gmail dot com

To solve this issue, a consortium of major NFT marketplaces around manifold.xyz agreed to deploy an industry-wide registry contract that collection builders can use to signal royalty splits independently from their token contracts. The Royalty Registry’s open source code base reveals that it supports many of the most important marketplace interfaces.

I don't have a direct answer for your questions but do suggest the canonical OAuth 2.0 implementation may be helpful for your learning too. LMK your thoughts. ➔ https://github.com/panva/node-oidc-provider

I could recommend https://github.com/panva/node-oidc-provider supports most of the oidc/oauth 2 rabbit hole specs.

This library forms the basis of a number of OIDC providers we, err, provide to our users.

You can also easily setup an OIDC server in Node using a certified OIDC lib like oidc-provider.

If it's nodejs auth servers you're after, look no further than here. Use it as-is, or as a library to build your own richer app.

You can take a look on node-oidc-provider

I am a little confused on how to implement an Auth server in node.js. There are plenty of libs that seem to do just that (ex: https://github.com/panva/node-oidc-provider) and then there's passport, which seems to be a full-fledged authentication framework? Will it serve my purpose or would it be overkill and I should just stick with simple libs like the one I mentionned. I can't seem to understand the difference between the two. Can someone explain?

SEEKING FREELANCER | Remote | NodeJS Dev with OpenID Connect experience

Looking for a NodeJS developer with OpenID / OAuth 2.0 experience to help with upgrading an OpenID Connect implementation. Specifically, the OpenID service depends on v6 of this library: https://github.com/panva/node-oidc-provider

We would like a review of our current implementation, and help with finishing a mostly-completed upgrade to v7 before we onboard 3rd-parties to our authentication and authorization infrastructure. We estimate the contract length to be between 1 - 2 months, part-time. To apply, send your CV and hourly rate to [email protected]. Please be sure to highlight your experience with the relevant technologies and protocols.

Have you looked for other OIDC/OAuth2 packages. Here's one in Node. That seems very interesting. https://github.com/panva/node-oidc-provider

I'm passing familiar with this area, but not as familiar as I should be...

How does this compare to something like this - https://github.com/panva/node-oidc-provider

Are they addressing the same need? Is Ory looking to get certified in these area? (Is it already?)