This content has been marked as final.
Show 4 replies
-
1. Re: queue authentication
marklittle Sep 13, 2007 1:37 PM (in response to poyge394)More information please.
-
2. Re: queue authentication
arutha Sep 14, 2007 9:40 PM (in response to poyge394)
Perhaps related, perhaps not, not sure what poyge394 asks:
Is there a way to make a 'whitelist' for queues, meaning only certain origins (IP/services/other) are allowed to put a message on the queue? (for clarity, the whitelist would contain the services/domains/IP's etc that are allowed to put something on the queue) -
3. Re: queue authentication
marklittle Sep 15, 2007 4:39 AM (in response to poyge394)You have complete control over your endpoint destinations. At present there's no such thing as ACLs, so when you publish them (the corresponding EPRs) in the registry every consumer can see them. When we integrate security aspects in a later release, you'll be able to define ACLs, roles etc. and the ESB will enforce them. But at the moment you'll have to do that yourself.
-
4. Re: queue authentication
burrsutter Sep 17, 2007 3:06 PM (in response to poyge394)
Is there a way to make a 'whitelist' for queues, meaning only certain origins (IP/services/other) are allowed to put a message on the queue? (for clarity, the whitelist would contain the services/domains/IP's etc that are allowed to put something on the queue)
If by queue you mean a JMS queue then this is really more a question for the JMS broker. Is your use case something like
messaging client produces a message -> JMS queue/topic -> ESB -> ESB mediates, transforms, routes, orchestrates, etc and sends the message to where it needs to go
Burr