Press Ctrl / CMD + C to copy this to your clipboard.
This post will be reported to the moderators as potential spam to be looked at
This might be a silly question but I am quite new to this aspect of authentication.
SImple question: Can this RestAPI also be used to authenticate members as well as users? If so, is there a sample somewhere?
Just to clarify. I of course mean using memberinfo to authenticate, not "user".
Could it be a simple case of switching these?
global::Umbraco.Core.Security.MembershipProviderExtensions.GetUsersMembershipProvider().AsUmbracoMembershipProvider());
to
global::Umbraco.Core.Security.MembershipProviderExtensions.GetMembersMembershipProvider().AsUmbracoMembershipProvider());
Or was that too simple :D
There is an issue on this topic in the github repo.
For now, you will have to come up with your own implementation using custom UmbracoApiControllers.
Ok, thanx. I guess the extension route is the right one then. I thought this was already in since it seemed possible to switch in custom.
What do you mean with the extension route?
It was suggested in the Github thread.
"It should be possible to extend the existing infrastructure to suite your requirements though.".
I guess this is a question of studying further :).
Good luck. :-)
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.
Continue discussion
RestAPI vs Members?
This might be a silly question but I am quite new to this aspect of authentication.
SImple question: Can this RestAPI also be used to authenticate members as well as users? If so, is there a sample somewhere?
Just to clarify. I of course mean using memberinfo to authenticate, not "user".
Could it be a simple case of switching these?
to
Or was that too simple :D
There is an issue on this topic in the github repo.
For now, you will have to come up with your own implementation using custom UmbracoApiControllers.
Ok, thanx. I guess the extension route is the right one then. I thought this was already in since it seemed possible to switch in custom.
What do you mean with the extension route?
It was suggested in the Github thread.
"It should be possible to extend the existing infrastructure to suite your requirements though.".
I guess this is a question of studying further :).
Good luck. :-)
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.