Propagating Standard Security Context through EBS and EBF Implementing Application Security Context

Working with Security 26-19 ■ Participating application information attributes: AIA:ParticipatingApp:Name - Name of the participating application AIA:ParticipatingApp:Version - Version of the participating application AIA:ParticipatingApp:SystemID - unique identifier of participating application ■ Application attributes: AIA recommends using this convention for naming the attributes for all the applications: Application name: attribute name. ■ Application neutral attributes: AIA recommends using AIA as prefix for all the application neutral attributes. These are the application neutral attributes identified so far: User : to represent user BusinessUnit : to represent organization or operating unit

26.7.7 Propagating Standard Security Context through EBS and EBF

The standard security context is inserted into the Enterprise Business Message EBM. As an EBM is propagated through various EBSs and EBFs to the destination ABCS, the security context is propagated along with the EBM to the target ABCS where it is used to propagate to the target application

26.7.8 Implementing Application Security Context

The following section provides the high level steps for implementing application security context on both the requester side and the provider side.

26.7.8.1 How to Implement Requester-Side Application Security Context

To implement requester-side application security context: 1. If an adapter is used, convert application security context information into XACML format in the adapter service. 2. If the application is sending information in data directly to the requester ABCS, convert the applications security context information to XACML format. 3. If new standard attributes are needed, work with internal architecture team. 4. Implement application context mapping service. 5. In the Requester ABCS, call the application mapping service to convert application specific app context information to application neutral app context information. 6. Call EBS.

26.7.8.2 How to Implement Provider-Side Application Security Context

To implement provider-side application security context: 1. Implement application context mapping service. 2. In the Provider ABCS, call application context mapping service to convert application neutral app context information to application specific app context information. 26-20 Developers Guide for Oracle Application Integration Architecture Foundation Pack 3. If you need to send information in data directly to provider application, convert applications security context information from XACML data to required form. 4. If an adapter is used, convert application security context information from XACML format to the required form in the adapter service. 27 Best Practices for Designing and Building End-to-End Integration Flows 27-1 27 Best Practices for Designing and Building End-to-End Integration Flows This chapter discusses best practices and recommendations for designing and building end-to-end integration flows. This chapter includes the following sections: ■ Section 27.1, General Guidelines for Design, Development, and Management of AIA Processes