Osman Elsayed
@osmanmelsayed.com
Software Engineer passionate about identity and access management. In a mission of making IAM better @ Visma e-conomic. Sudanese 🇸🇩 that found his home in the vibrant tech hub of Copenhagen 🇩🇰.
It would also be nice to visualize what does my license allow me to do. That can be in a self-service portal, or something like that.
December 12, 2024 at 11:52 AM
It would also be nice to visualize what does my license allow me to do. That can be in a self-service portal, or something like that.
I'd just say:
- Consider adding an OOTB license heath check. It'd be a nice compliment to the graceful behavior of the license validation. So, if the lincese isn't available in prod, then it's easier to notice for devs. Also consider bundling it with (docs.duendesoftware.com/identityserv...).
- Consider adding an OOTB license heath check. It'd be a nice compliment to the graceful behavior of the license validation. So, if the lincese isn't available in prod, then it's easier to notice for devs. Also consider bundling it with (docs.duendesoftware.com/identityserv...).
Duende Software Documentation
The most flexible and standards-compliant OpenID Connect and OAuth 2.0 framework for ASP.NET Core.
docs.duendesoftware.com
December 12, 2024 at 11:51 AM
I'd just say:
- Consider adding an OOTB license heath check. It'd be a nice compliment to the graceful behavior of the license validation. So, if the lincese isn't available in prod, then it's easier to notice for devs. Also consider bundling it with (docs.duendesoftware.com/identityserv...).
- Consider adding an OOTB license heath check. It'd be a nice compliment to the graceful behavior of the license validation. So, if the lincese isn't available in prod, then it's easier to notice for devs. Also consider bundling it with (docs.duendesoftware.com/identityserv...).
Thanks for reaching out @jmdc.dev!
I'm happy with the current license validation logic. It strikes a good balance between being graceful enough (prod won't stop working if the license expires) and being restrictive enough (advanced features won't work without a valid license in prod).
I'm happy with the current license validation logic. It strikes a good balance between being graceful enough (prod won't stop working if the license expires) and being restrictive enough (advanced features won't work without a valid license in prod).
December 12, 2024 at 11:46 AM
Thanks for reaching out @jmdc.dev!
I'm happy with the current license validation logic. It strikes a good balance between being graceful enough (prod won't stop working if the license expires) and being restrictive enough (advanced features won't work without a valid license in prod).
I'm happy with the current license validation logic. It strikes a good balance between being graceful enough (prod won't stop working if the license expires) and being restrictive enough (advanced features won't work without a valid license in prod).