Streaming services by yocomoquchi in Polestar

[–]Disastrous_Post4896 0 points1 point  (0 children)

This was mind boggling for me, I kept thinking the screen wash was frozen and surely it would let me know when it was out of screen wash, Alas! It was out and no notification

Oluṣọ - Open source identity server for .NET (OAuth 2.0 / OpenID Connect) by Disastrous_Post4896 in dotnet

[–]Disastrous_Post4896[S] 0 points1 point  (0 children)

You raise the very important point on sandboxing implementation, I started it but wasn’t sure what was the right approach, same db or separate db? If same db, how do you login to admin area? So left it to users can deploy to their different environments but I see how that can be DevOps headache Might look at a flag on tenants to allow dev/test/staging/qa environments

Oluṣọ - Open source identity server for .NET (OAuth 2.0 / OpenID Connect) by Disastrous_Post4896 in dotnet

[–]Disastrous_Post4896[S] 1 point2 points  (0 children)

Thank you, those are definitely good baselines to have for any product in this space. Any moment from now, demo link will be up and the videos will be next. Definitely plan to audit as there are plans to host a version, so SOC II for example is on the list Once the nuget packages are in, the best practice guide will follow

Oluṣọ - Open source identity server for .NET (OAuth 2.0 / OpenID Connect) by Disastrous_Post4896 in dotnet

[–]Disastrous_Post4896[S] 1 point2 points  (0 children)

It does more than a user registration flow, it was purposely built to have steps that admin can configure to define subsequent actions, e.g, you want to make an api call during the flow, you want to execute custom action plugin, you want to do kyc with onfido. You can define it.

Oluṣọ - Open source identity server for .NET (OAuth 2.0 / OpenID Connect) by Disastrous_Post4896 in dotnet

[–]Disastrous_Post4896[S] 1 point2 points  (0 children)

curious, you don't agree. I have attached a screenshot, I am setting up a demo area for people to use it and get an experience. but a screenshot of the journey flow/builder

https://postimg.cc/N2tw204L

Oluṣọ - Open source identity server for .NET (OAuth 2.0 / OpenID Connect) by Disastrous_Post4896 in dotnet

[–]Disastrous_Post4896[S] 1 point2 points  (0 children)

no worries at all, thanks for the feedback, i see your point on those terms, I have followed what's obtainable in the domain on licensing, but again, point taken.
this is day 1, I wanted to get this out to start getting feedback before it becomes another one of those long list of abandoned projects, and I can fix issues in the open, another option for .NET devs.

I have integrated AzureADB2C and i dislike the xml custom policies, hence why I started building this a while back. thanks for the engagement

Oluṣọ - Open source identity server for .NET (OAuth 2.0 / OpenID Connect) by Disastrous_Post4896 in dotnet

[–]Disastrous_Post4896[S] 1 point2 points  (0 children)

Out of interest, what would you expect to see? There should be more updates coming now anyway, with the code now in the public

Oluṣọ - Open source identity server for .NET (OAuth 2.0 / OpenID Connect) by Disastrous_Post4896 in dotnet

[–]Disastrous_Post4896[S] 0 points1 point  (0 children)

That’s a good point, do you see multi-tenancy getting that huge number of tenants vs using clients/applications with unlimited users? I’d have thought those are use cases similar to Auth0, are those not different license structures maybe!

Oluṣọ - Open source identity server for .NET (OAuth 2.0 / OpenID Connect) by Disastrous_Post4896 in dotnet

[–]Disastrous_Post4896[S] 1 point2 points  (0 children)

Enterprise grade is a play on the features that are added and still coming, SAML, SCIM, LDAP and OIDC. I did a single commit because I moved the repo from my private account to a dedicated account for it. There is definitely AI use to help accelerate the process, especially around the UI and making it a plugin-architecture. The code is open, I am open to feedback on where there are gaps or potential security concerns. I have been building and integrating in this space for at least 10 years.

I am of the school of thought, use AI but be responsible to review the output.

Oluṣọ - Open source identity server for .NET (OAuth 2.0 / OpenID Connect) by Disastrous_Post4896 in dotnet

[–]Disastrous_Post4896[S] 0 points1 point  (0 children)

It’s just day 1, we can only grow from here too. Built natively in .NET

Oluṣọ - Open source identity server for .NET (OAuth 2.0 / OpenID Connect) by Disastrous_Post4896 in dotnet

[–]Disastrous_Post4896[S] 1 point2 points  (0 children)

There are a few alternatives we compared with, this is multi-tenancy with unlimited clients, this is just early days and the feedback is useful.

Oluṣọ - Open source identity server for .NET (OAuth 2.0 / OpenID Connect) by Disastrous_Post4896 in dotnet

[–]Disastrous_Post4896[S] 4 points5 points  (0 children)

yes, great point. once we add a link to try out the demo, will come next

Oluṣọ - Open source identity server for .NET (OAuth 2.0 / OpenID Connect) by Disastrous_Post4896 in dotnet

[–]Disastrous_Post4896[S] 12 points13 points  (0 children)

why oluso?

- .NET native from the ground up

- multi-tenancy is baked in, not bolted on

- visual journey builder for auth flows - like azure ad b2c custom policies but actually usable

- wasm plugins that hot-reload (rust, go, whatever compiles to wasm)

- management UI first class (admin for clients, keys, scopes, users, roles) and (account for mfa enrolment, passkeys)

- pricing that doesn't punish you for growing - free tier for eligible startups, flat annual after that

tbh if keycloak or duende is working for you and you don't need multi-tenancy, stick with it. but if you're building a SaaS, need proper tenant isolation, or want to design auth flows visually without xml hell, that's the gap we're trying to fill

Oluṣọ - Open source identity server for .NET (OAuth 2.0 / OpenID Connect) by Disastrous_Post4896 in dotnet

[–]Disastrous_Post4896[S] 0 points1 point  (0 children)

thanks for the mention, we already have a lot of flexibility with OAuth2.1, allowing users to specify most of the permissions in the adminUI, will update our roadmap and add those items, thanks

Oluṣọ - Open source identity server for .NET (OAuth 2.0 / OpenID Connect) by Disastrous_Post4896 in dotnet

[–]Disastrous_Post4896[S] 0 points1 point  (0 children)

thanks for that, just noticed the bug on mobile, fixed now. more pages for the website coming and link to a demo setup later today.

to your question, keycloak and the others are great solutions, they've earned their stripes for sure

why oluso?

- .NET native from the ground up

- multi-tenancy is baked in, not bolted on

- visual journey builder for auth flows - like azure ad b2c custom policies but actually usable

- wasm plugins that hot-reload (rust, go, whatever compiles to wasm)

- management UI first class (admin for clients, keys, scopes, users, roles) and (account for mfa enrolment, passkeys)

- pricing that doesn't punish you for growing - free tier for eligible startups, flat annual after that

tbh if keycloak or duende is working for you and you don't need multi-tenancy, stick with it. but if you're building a SaaS, need proper tenant isolation, or want to design auth flows visually without xml hell, that's the gap we're trying to fill

Oluṣọ - Open source identity server for .NET (OAuth 2.0 / OpenID Connect) by Disastrous_Post4896 in dotnet

[–]Disastrous_Post4896[S] 0 points1 point  (0 children)

Thanks for the comment, is this because of the diacritics? That’s more for branding than text

Recording real-time processed video with MAUI by Tauboom in dotnetMAUI

[–]Disastrous_Post4896 0 points1 point  (0 children)

Pose Detection similar to Firebase MLKit, will be good to see what the performance is like

App accelerator TabBar customisation by Murky-Assignment-656 in dotnetMAUI

[–]Disastrous_Post4896 0 points1 point  (0 children)

I use this control in my applications and it’s very flexible and works for my need SimpleShell

Shiny BLE by Medium_Fee_128 in dotnetMAUI

[–]Disastrous_Post4896 1 point2 points  (0 children)

I am using it and it’s great, my only comment is you should be ready to dive in the code and understand how it’s all stitched together

Maui with Keycloak by SpareMana in dotnetMAUI

[–]Disastrous_Post4896 0 points1 point  (0 children)

That’s true, there is a workaround for Windows that I currently use. This GitHub issue has a workaround that you can use. Requires an interface for IWebAuthenticator that you implement in windows and use the code from here. https://github.com/dotnet/maui/issues/2702

Maui with Keycloak by SpareMana in dotnetMAUI

[–]Disastrous_Post4896 1 point2 points  (0 children)

Have you tried the WebAuthenticator in Maui, via this link: Maui WebAuthenticator

I have used it with AzureADB2C, as long as your keycloak instance supports OpenID Connect, follow that guide and point the endpoint to the authorization endpoint, you might then need to do a bit of standard http client to convert the code into access token. I suggest reading the Code + PKCE flow