Sep 24

rel="File-List" href="file:///C:%5CUsers%5Cpebble%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_filelist.xml"> rel="themeData" href="file:///C:%5CUsers%5Cpebble%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_themedata.thmx"> rel="colorSchemeMapping" href="file:///C:%5CUsers%5Cpebble%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_colorschememapping.xml">

I get up very early this morning so have been here at a very early time .Now is 9:22 am. I think I should think about what the project of credentials management is for and the whole structure from the macro point.

Background Knowledge:

    When the client want to do some action in the server , the server should check whether the client have the right or the certificate on it. So how to save the roles and their certificates become a problem. It is said that it is easy for us to use asp.net provider to save and modify the accounts and the roles. I think the CM service of the project is to pack the functions of how the asp.net provider operate the DB which is security-related.

 

The use of C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/aspnet_regsql.exe

  Create or configures a sql server database that stores information for asp.net applications services.(membership, profiles, role management, personalization ,and Sql web event provider.)

 

Now I want to explain the whole structure of the structure. In this project there are two layers. One Is the data access layer, which is more closer to the DB. And the second is Interfaces for the clients or users. The data access packs the api of Data provider like DataSet for .net. and the interfaces packs the membership class and membershipprovider and so on which is in the namespace of web.security. Maybe just for this it is called providers for credentials management.