How to prevent TMA clients from publishing/subscribing on services not defined?
Article ID: KB0094442
Updated On:
| Products | Versions |
|---|---|
| TIBCO Messaging Appliance P-7500 | - |
| Not Applicable | - |
Description
Resolution:
Environment
===========
TMA
Description
===========
Out-of-box TMA defines a default entry of Username Service Mappings, which contains empty username, empty service and ACL profile "default". This will allow any client to create transports and publish/susbcribe on any service.
Resolution
===========
Remove this "default" mapping, and add customized mappings such as:
--------
username: <empty>
services: 8600
profile name: default
--------
Now all clients will be able to publish/subscribe on service 8600 only. You may add more such mappings if you want to allow more services.
Environment
===========
TMA
Description
===========
Out-of-box TMA defines a default entry of Username Service Mappings, which contains empty username, empty service and ACL profile "default". This will allow any client to create transports and publish/susbcribe on any service.
Resolution
===========
Remove this "default" mapping, and add customized mappings such as:
--------
username: <empty>
services: 8600
profile name: default
--------
Now all clients will be able to publish/subscribe on service 8600 only. You may add more such mappings if you want to allow more services.
Issue/Introduction
How to prevent TMA clients from publishing/subscribing on services not defined?
Feedback
Yes
No
Powered by
