Problem with SYSDBA

[jrheisler]

There appears to be an issue with sysdba ConnectAs as it is used in TOracleSession and TOracleLogon.

1. If you set the TOracleSession.ConnectAs = caSYSDBA, the set the TOracleLogon.Options idConnectAs := False then TOracleLogon.Execute with SYS it will not set the ConnectAs to caSYSDBA. It will only work if you set TOracleLogon.Options idConnectAs := True. Then it works fine.

2. You can logon in both the ide and run time as SYS SYSDBA using any password at all.

Thanks
Jeff jrheisler@yahoo.com

 

[Marco Kalter]

1. If you set the TOracleSession.ConnectAs = caSYSDBA, the set the TOracleLogon.Options idConnectAs := False then TOracleLogon.Execute with SYS it will not set the ConnectAs to caSYSDBA. It will only work if you set TOracleLogon.Options idConnectAs := True. Then it works fine.

That's how the ldConnectAs option is defined.

2. You can logon in both the ide and run time as SYS SYSDBA using any password at all.

I am not sure how that would work.

 

[jrheisler]

Marco,

Thanks, number 1 I was assuming would be the case, but number 2, so baffling. It really allows you to connect using any password. You can even attach a TOracleDataset to the session and have full access to the table. That can not be what is intended?

Thanks
Jeff

 

[Marco Kalter]

I think this is an OS Authentication security setup somewhere, and I assume you can also connect like this with any Oracle Net tool (e.g. SQL*Plus).

 

[jrheisler]

Marco,

SQLPlus does not allow connecting via the sys user without the proper password.

Any other thoughts?

Thanks
Jeff