Welcome to Questionaries, where you can ask questions and receive answers from other members of the community.

Let us know at info@questionaries.org

Why are OPS$ accounts a security risk in a client/server environment for DBA ?

3 like 0 dislike
Hello guys,

Why are OPS$ accounts a security risk in a client/server environment for DBA ?
Please give me your feedback

Thanks in advance
asked 1 year ago by daneim (127,080 points)

1 Answer

1 like 0 dislike
 
Best answer
If you allow people to log in with OPS$ accounts from Windows Workstations, you cannot be sure who they really are. With terminals, you can rely on operating system passwords, with Windows, you cannot.
If you set REMOTE_OS_AUTHENT=TRUE in your init.ora file, Oracle assumes that the remote OS has authenticated the user. If REMOTE_OS_AUTHENT is set to FALSE (recommended), remote users will be unable to connect without a password. IDENTIFIED EXTERNALLY will only be in effect from the local host. Also, if you are using "OPS$" as your prefix, you will be able to log on locally with or without a password, regardless of whether you have identified your ID with a password or defined it to be IDENTIFIED EXTERNALLY.
answered 1 year ago by marck_don (191,010 points)

Related questions

13 like 1 dislike
1 answer
9 like 0 dislike
1 answer
asked 1 year ago by hunter (5,930 points)
2 like 0 dislike
1 answer
4 like 0 dislike
1 answer
4 like 0 dislike
0 answers