Umbraco Authorized Services is an open-source package designed to reduce the effort needed to integrate third party services that require authentication and authorization via an OAuth flow.
It would be great to define the authorization information but have an option to define if ti is a a login authorization or API access information and then handle accordingly.
It would be great to define member or user integration and then provide information and documentation to easily manage the login similar to what is outlined with the Authorization.
I do not have time currently but this package for me has a lot of possibility and could be big for Umbraco. I am visioning if this also supported a GraphQL output build where a layer with peoples support they could build out info for what output responses are and offer a model to easily consume them directly so a lot easier for everyone else to request and manage the data. One request, reading that products API output is straight forward but when it comes to managing multiple requests etc it does become harder... Offering something that takes the load of would increase the appeal to users greatly.
I was working on a similar concept for a now EOL platform from Adobe. Providing similar credential data and then defining an endpoint from that service and then providing a complete JSON sample through the backend interface the solution would then know make the endpoint request and then respond correctly and called and managed easily through the liquid markup language.
Hi All, We have this - https://docs.umbraco.com/umbraco-cms/reference/security/external-login-providers But with the concepts outlined in this package I was wonder if this could be expanded to a bit more?
It would be great to define the authorization information but have an option to define if ti is a a login authorization or API access information and then handle accordingly. It would be great to define member or user integration and then provide information and documentation to easily manage the login similar to what is outlined with the Authorization.
I do not have time currently but this package for me has a lot of possibility and could be big for Umbraco. I am visioning if this also supported a GraphQL output build where a layer with peoples support they could build out info for what output responses are and offer a model to easily consume them directly so a lot easier for everyone else to request and manage the data. One request, reading that products API output is straight forward but when it comes to managing multiple requests etc it does become harder... Offering something that takes the load of would increase the appeal to users greatly. I was working on a similar concept for a now EOL platform from Adobe. Providing similar credential data and then defining an endpoint from that service and then providing a complete JSON sample through the backend interface the solution would then know make the endpoint request and then respond correctly and called and managed easily through the liquid markup language.