Re: Block connection from SQL developer

Hi Thomas,

we dont want to enforce changes from db end , no modification on DB side is required, any changes or restrictions from client to restrict from sql developer will be helpful .

Regards,
Krishna

On Fri, 11 Mar 2022 at 18:08, Thomas Kellerer <dmarc-noreply_at_freelists.org> wrote:

> V$SESSION.PROGRAM is provided by the client - so you can't trust it.
>
> I can make a Java program appear as "SQL*Plus" in V$SESSION.PROGRAM - or
> even "oracle.exe"
>
>
> John Thomas schrieb am 11.03.2022 um 13:23:
> > You could have a database logon trigger that raises an error if the
> user's V$SESSION.PROGRAM is SQL Developer.
> >
> > Depends on your requirement though. If you have privileged users with
> other means of access - SQL*Plus for instance - they could easily disable
> the trigger.
> >
> >
> > Regards,
> >
> > John Thomas
> >
> >
> > On Fri, 11 Mar 2022 at 12:08, Krishnaprasad Yadav <
> chrishna0007_at_gmail.com <mailto:chrishna0007_at_gmail.com>> wrote:
> >
> > We are in a requirement that certain database instances should
> not connect from sql developer.
> > incase of 40 Database we can connect 36 by sql developer and
> remaining 4 database should not connect by SQL developer .
> >
> > Is their any sort of Setting or any other alternative available in
> SQL developer .
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>

--
http://www.freelists.org/webpage/oracle-l