Skip to main content

70-562 Membership API




Membership class: Provides the api to manage users, create, find, generatePassword, ValidateUser, and more...

MembershipUser Class: Stores name, email, password, question/answer, but doesnt manager user defined properties like profiles GetPassword, ResetPassword, UpdateUser, properties describing user info. One could make a page that allows to find users, delete user, select user from a listView control, which would provide a details view and update a password, or button to reset it.

Managing users from your own interface instead of configuration manager or web.config

API: MembershpiCreateStatus, Membership.Createuser(...), Membership.GetallAllUsers() retunrs an array of users. Membership.DeleteUser(strUserName), MembershipUser user = Membership.GetUser(strUserName), user.ChangePassword(old, new),
user.ChangePaswwrdQuestionAndAnswer(...), Membership.FindUsersByEmail(strUserName), Membership.FindUserByName(strUserName), user.ResetPassword(oldPassword), Managing Roles from your own interface instead of configuration manager or web.config

Roles Class: AddUser(s)ToRole(s)(...), CreateRole/DeleteRole, GetUsersInRole retrieves MembershipUsers objects, FindUsersInRole returns juste the names, GetRolesForUser/IsUserInRole, GetAllRoles returns a list of roles, RemoveUser(s)FromRole(s), RoleExists(s).

The delete from role method will delete user(s) from the role, and there is also another method that deletes the role itself or throws an exception if there is a user in this role.

Creating a custom provider

Membership and roles layer are based on the provider concept, that, API abstracted from data acesss layer. To create a provider that doesnt use sql server or express, you'd add a class to the App_Code folder. Inherti fromSystem.Web.Security.MembershipProvider or RoleProvider, Provide all the code for each of the methods, they map one to one to the API and you need to supply them all if you're creating your own provider. When inherting from the provider, let visual studio create the member stubs by right clicking on the class you inherit from, it will insert all the mothods you need to implement.

Membership controls vs custom providers

The controls have a property that indicates wich provider to use. You can also create your own controls and use the

Membership and roles API.



Comments

Post a Comment

Popular posts from this blog

React JS Patterns

React JS is always evolving, and evolving quickly. These evolutions can be very significant ones, for example, the addition of hooks. React has a lot of code patterns, often these patterns are motivated by the DRY and/or the open-close principle. These patterns sometimes come in to replace a previous one, yet the previous ones still stays in use, as a consequence, the list of patterns keep growing. The goal of the next few posts will be to list the patterns commonly used in React JS developpement. Some patterns are more specific to JSX and I will start with these, and maybe add patterns specific to Redux.
4 comments
Read more

Rxjs Forkjoin vs Zip

These Rxjs combination operators are handy to make Rest calls in parallel and combine their results. Both take n observables and will return the results, with the difference that forkJoin will complete even if one of the nested observables errors of completes.
Post a Comment
Read more

Object.create vs. Object.Assign

The two functions return a new Object but with a difference. Object.assign will go through an enumerable and copy it's properties. Object.create will create a new empty object but link it's proto chain to the old object. One way to view this is with JSON.stringify(newCreatedObject) this would return an empty object, since all the properties are not part of the object's own properties, but inherited through prototype inheritance. In both case, the advantage is it allows to extended existing objects without modifying the original. This is particularly important when receiving arguments from a caller, in this case it's better to use these methods instead of modifying the caller's object since he might have planned to use it again later, expecting it to be in it's original state.
Post a Comment
Read more