yxes2013 wrote:Nonsensical question. SQL-Developer does not listen on a network port. The port it uses will be a client port in the dynamic port range - created when SQL-Developer connects to the Listener port on the Oracle server.
I want to secure port for my Sqldeveloper which is on my laptop with IP 220.127.116.11 to connect to a scecured PROD server SLES 11.
Billy Verreynne wrote:Agreed. At my last job a directive came down from higher in the organization mandating we use it. It was such a PITA that the field offices (one of which was where I worked) ended up just ignoring it.
An option/feature I dislike... In my view IP based security of that nature belongs further down in iptables, and not as some dorky Listener setting. Never really understood why Oracle had that as a Listener feature.
yxes2013 wrote:SQL-Developer is a client. The database is a server. Firewall in-between.
My point is, can I use sqldeveloper & OEM to monitor ah highly secure database? where every connection is being filtered in a complex firewall?
sybrand_b wrote:True enough, but in the case I cited, the directive was specifically to use tcp.invited_nodes. An example of ham-fisted, clueless policy.
Connection Manager -which is not installed in a typical install -allows subnets.
Senior Oracle DBA