Access Management for Web Applications
A series of blogs has been put up by Maria Sum at Sun Microsystems. The seven part series discusses the Sun products for security and access control. These are the products that have been selected in the Draft Specification for the Security & Access Control module.
In the Draft Specification, the Security & Access Control module is also the first module to be built. Using Sun Identity, Federated and Access Management frameworks. How this is implemented in the People, Ideas & Objects application modules is that we will be building the application module almost immediately. It will then be used by the community to test and develop the module to the needs of the community. Making the module so that it is Single Sign On (SSO) and that everyone in the community has a hands on understanding and use of the module right from the start.
This is certainly a different way of developing the application, usually the Security & Access Control are the last things that are cobbled together as an after thought. Sun has something to say about that and the use of their product frameworks.
Typically, the number-one problem in developing Web applications is that identity is often an afterthought," Jamie observes. "Developers tend to focus on the logic, UI, and other aspects until it dawns on them, toward the end of the cycle, that they must secure the applications for, say, user login's and protect the data. Then come the important questions of what tools to use for verifying and authorizing access, what maintenance tasks are involved, whether to adopt federated identity—all afterthoughts at the eleventh hour.The security of the information held within the People, Ideas & Objects application modules is of a mission critical, highly sensitive and confidential basis. Add to the fact that we are interacting between the community, the producers and their partners and all members of the service industry the security of the system becomes the number one priority. This also brings up the nature of the code that is compiled into the module. This needs to be open and reviewable by those that use the code. It is not enough to say "trust me", people, producers and suppliers have to be able to independently verify that the security level is achieved through their own review. And in People, Ideas & Objects the source code is available to the community and producers for just this purpose.
As with most of Sun's products this independent review of the source code is available to their products. Sun is strongly committed to Open Source Software and therefore their code is openly reviewable as well as that of the People, Ideas & Objects application modules. These products include the following four components.
- Sun Java System Access Manager
- Sun Java System Federation Manager
- Sun Java System Directory Server
- Sun Java System Identity Manager
By implementing the application early, we are able to use the SSO as the method that our community accesses "Google Apps for People, Ideas & Objects Domain" and "SalesForce.com". Permitting our Users to sign on once and have access to all of our systems with one very secure sign in page. Early use will educate our users on its value and features and debug our implementation. Ideally we will need to have the authentication, verification and audit procedures and policies in place before the system is provided to our customers. A system that is used by all members of the community first, and then as production code for our producer clients.
I want to stress a major point of how this application, as defined, is implemented in the greater scheme. If producers are not satisfied with the level of security offered, they are able to deal with the Users and Developers directly to get the solution they want. Try that with either Oracle or SAP. It is reasonable therefore we will have the most secure system possible operating in the ERP market space. And yet, by using Sun's products in this fashion we inherit the following.
Again, Jamie emphasizes, The goal is to free up developers to do their primary jobs instead of fiddling with security.and
Jamie strongly advocates access management being part of the application design. Applications that work centrally with access management are the answer, he says; otherwise, "you end up creating a load of mundane and unnecessary work for professional-service engineers and system integrators." Typically, as in health-care applications, you "retrofit or use a wedge to incorporate SSO into applications."This is the model that Sun uses to provide the product. What Sun's Chief Open Source Officer calls the try-prototype-buy support model. Making the extensive costs of developing a high level system such as this much more affordable for development. Interestingly Sun states this in two different phases of a development projects life cycle. When you have time but no money, free is great, and when you have more money then time, the Sun services are there to provide the support.
In Part 5 of the series Sun engineers talk about the "build" model of how the applications go from Open Source to commercial release. The feature differences between the different builds and the expectations from each product. They also state that the application when used in an environment such as People, Ideas & Objects, should have the most recent version of the Sun products.
Lastly I don't expect this preliminary operating feature consider the Military Command & Control Metaphor, or digital signing of documents like agreements and A.F.E.'s in this first build of the module.
I will be adding this information to the Draft Specifications for the Security & Access Control module in the wiki. To begin this development we need to have our targeted audiences, the oil and gas investor that is disgruntled by the bureaucracy, and governments that need to resurrect the economy, provide the financial resources. If you know of someone that meets that requirement, please send them the URL to this website and encourage them to contribute, and join me here.
Technorati Tags: People's Sun Specification Software