You wish to restrict access to a JMS queue so that only specific accounts may receive messages
from the queue. Identify two steps that, when performed together, implement this security
requirement.
A.
Create a policy for queue’s URL pattern.
Login into the Admin server console –> Navigate to the Queue that needs to be secured.
B.
Add a policy to the queue and associate it with a role.
Click on the security tab –> Policies sub tab.
You can see a small drop down list, which lists the set of the operations that can be protected.
C.
Configure an identify assertion provider.
Click Add Conditions to add the policy conditions.
D.
Acquire the domain configuration lock.
From the predicate list, specify the policy conditions.
E.
Create a global role and assign users to it.
Specify the role (the global created in E below) which needs to have the access permissions for
the JMS Queue. Click Add –> Finish.
E: Create a Global Role and assign the appropriate user accounts to it.
Note: There are two ways of securing the JMS resources.
A.
Create a policy for queue’s URL pattern.
Login into the Admin server console –> Navigate to the Queue that needs to be secured.
B.
Add a policy to the queue and associate it with a role.
Click on the security tab –> Policies sub tab.
You can see a small drop down list, which lists the set of the operations that can be protected.
C.
Configure an identify assertion provider.
Click Add Conditions to add the policy conditions.
D.
Acquire the domain configuration lock.
From the predicate list, specify the policy conditions.
E.
Create a global role and assign users to it.
Specify the role (the global created in E below) which needs to have the access permissions for
the JMS Queue. Click Add –> Finish.
E: Create a Global Role and assign the appropriate user accounts to it.
Note: There are two ways of securing the JMS resources.
Explanation:
B:
Security policy for a JMS Queue (Resource Level).
When you define a security policy for an individual destination on a JMS server, you can protect all
operations of the destination.
Reference: SECURING WEBLOGIC JMS RESOURCES