A development team has been notified that all the requests serviced by their SOAPInput node message flow will now contai
Posted: Fri Aug 26, 2022 9:58 am
A development team has been notified that all the requests serviced by their SOAPInput node message flow will now contain wsse headers for authentication, encryption and signatures. The system administrator created the security profile with authentication set to use LDAP and asked the development team to associate the flow's BAR file with the security profile and redeploy it to the broker. When the requests were sent to the broker, they were not processed. What did the system administrator miss?The system administrator missed: 1. creating the policy set
A. 2. creating the consumer policy set binding3. putting key information in the policy set4. adding the private keys to the keystore5. pointing the broker to it and giving the names of the policy set and the policy set binding to the developers forassociating them with the BAR file before the redeploy
B. 2. creating the provider policy set binding3. putting the key information in the policy set binding4. adding the private keys only to the keystore5. pointing the broker to it and giving the names of the policy set and the policy set binding to the developers forassociating them with the BAR file before the redeploy
C. 2. creating the consumer policy set binding3. putting the key information in the policy set4. adding the private and public keys to the keystore and truststore5. pointing the broker to them and giving the names of the policy set and the policy set binding to the developers forassociating them with the BAR file before the redeploy
D. 2. creating the provider policy set binding3. putting the key information in the policy set binding4. adding the private and public keys to the keystore and truststore5. pointing the broker to them and giving the names of the policy set and the policy set binding to the developers forassociating them with the BAR file before the redeploy
A. 2. creating the consumer policy set binding3. putting key information in the policy set4. adding the private keys to the keystore5. pointing the broker to it and giving the names of the policy set and the policy set binding to the developers forassociating them with the BAR file before the redeploy
B. 2. creating the provider policy set binding3. putting the key information in the policy set binding4. adding the private keys only to the keystore5. pointing the broker to it and giving the names of the policy set and the policy set binding to the developers forassociating them with the BAR file before the redeploy
C. 2. creating the consumer policy set binding3. putting the key information in the policy set4. adding the private and public keys to the keystore and truststore5. pointing the broker to them and giving the names of the policy set and the policy set binding to the developers forassociating them with the BAR file before the redeploy
D. 2. creating the provider policy set binding3. putting the key information in the policy set binding4. adding the private and public keys to the keystore and truststore5. pointing the broker to them and giving the names of the policy set and the policy set binding to the developers forassociating them with the BAR file before the redeploy