I'm building a custom ASP.NET membership provider to get its users from the Tessitura web API. Does anyone have experience with this (or source code examples) that they could share? Here are some general ideas that I have in mind:
- Make the Tessitura proxy object (web API client) a static member of the custom MembershipProvider class to prevent multiple instantiations.
- Give the custom MembershipProvider its own static Tessitura session key to prevent spawning tons of unnecessary Tessitura session keys when anonymous constituents want to browse the site.
I'm hoping someone can offer a bit more insight or alternatives.
Thanks,Bryan
Hi Bryan,
I wondering how you made out with this. I am looking at creating a custom membership provider as well. I also looked at just using a custom Authrize attribute as well.
Thanks ,
Jon
Actually, I ended up abandoning the idea. The Tessitura Web API doesn't expose its data in a way that works well with ASP.NET's custom membership provider classes. I've ended up creating something more like a data abstraction layer and a custom, static "WebClient" class. The WebClient class handles Tessitura session keys, anonymous users, authentication, and carts using browser session variables. In many ways, it resembles an ASP.NET membership provider, but it doesn't extend that class.
This is actually something which will be MUCH easier to do with the v11 Next Generation API, which will support most of the operations required by System.Web.Security.MembershipProvider.
Some notable exclusions would be GetAllUsers, GetPassword and support for password question and answer.
Other methods like CreateUser, ValidateUser, UpdateUser, GetUser, GetUserNameByEmail, ChangePassword, ResetPassword, UnlockUser can easily be implemented using the new REST API.
Normal 0 false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4