Abstract
During interactions between organizations in the field of service-oriented architecture, some security requirements may change and new security policies addressed. Security requirements and capabilities of Web services are defined as security policies. The purpose of this paper is reconciliation of dynamic security policies and to explore the possibility ofrequirements of the new defined securitypolicies. During the process of applying the defined dynamic policy, is checked whether the service provider can accept the new policy or not. Therefore, the compatibility between existing policies and new defined policies are checked, and because the availablealgorithms for sharing between the two policies, resulted in duplication and contradictory assertion, in this paper for providing a compromise betweenthe provided policy and the new policy, the fuzzy inference method mamdany isused . and by comparing the security level of proposed policy with the specified functionality, the negotiating procedure is done . The difference between the work done in this paper and previous works is in fuzzy calculation and conclusion for negotiations. the advantages of thi work is that policies are defined dynamicallyand applied to bpel , also can be changedindependently of bpel file.
Highlights
To determine which web service is appropriate for a specific application, functional capabilities should be adapt able with functional requirements and non-functional capabilities in Web service should meet non-functional requirements
In this paper a framework is proposed to attach a new policy to bpel activitiy dynamically and negotiate between requester and provider
Among the advantages that can point for the proposed framework, is that external attachment of policies to bpel distinct the business process logic from describtion of quality of service
Summary
To determine which web service is appropriate for a specific application, functional capabilities should be adapt able with functional requirements and non-functional capabilities in Web service should meet non-functional requirements. Consumer and provider of Web services, define their requirements and security policies as XML files named ws-policy. WSpolicy provides a basic structure to describe a wide range of requirements and capabilities of Web services. The changes are security changes and while applying new policies to processes , check whether the service provider will be accept the new policy or not. In part 2, the structure of policies is defined. In part 3, the framework will be described and check the ability to dynamically negotiate on new policy. If the negotiation success , the new policy will be dynamically applied. Section four presents the conclusions and suggestions for future deals
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
