This project is read-only.

orchard overrides and module development

Topics: Core, Customizing Orchard, General, Writing modules
Jun 7, 2016 at 4:04 PM
Am I right in thinking that most of the "services" are one and only?

eg: if you wanted to support multiple authentication methods you would need to, somehow, cater for that yourself because you can't just say"

"add authentication service 1"
"add authentication service 2"
so that you could provide (for example)
"try to login with User/Pass for service 1, if that passes then you are logged in, if it fails then try with service 2... and so on...

in that you need to target a service and then suppress the "orchard" one...

Or am I missing something that allows you to do this?
Jun 10, 2016 at 9:16 AM
Most of them are, unless they are designed to support providers/events.
Examples of services employing a provider/event approach are content handlers and authorization handlers.

I think it would be nice if the MembershipService in your example would employ such a model. Right now you would have to suppress it and implement your own authentication logic.
Marked as answer by smerlon on 6/12/2016 at 8:22 PM
Jun 13, 2016 at 4:22 AM
Cool... thanks for the info.
I've create such a thing now (custom membershipservice)... thanks.
(Aside: U recommend any tut's or suggested code samples (existing modules) to look at (good) authorization handlers usage?)