[Info-ingres] Installation Password vs DBMS Authentication

[Paul White]

Hi Steve,

I think the installation password is designed to be used in a protected 
network environment where you are in control of the enduser names.  The 
authentication matches the client OS user with a DBMS user and optional 
password.

Most of my sites use Server and Database users with hard coded vnodes 
and DSNs.   At one site, we have a development effort to migrate towards 
a combination of installation password, app/role passwords and some user 
passwords.   We have been experimenting with 2FA and temporary passwords 
to act like a token.  It seems reasonably secure.

  * OpenROAD challenges AppUser + password,
  * Sends a message to the security service to allow a match on Device,
    Active Directory User/Group, Application, AppUser, password.
  * If matched ok, the service:
  * - refreshes the the database user: expiry date and temporary password.
  * - sends an SMS with 4-6 digit pin to nominated mobile number.
  * - responds to OpenROAD with a one time token
  * The user enters the pin which combines with the token to be used as
    the database password
  * OpenROAD connects to the database.
  * Application logic uses role/password to allow access to various tables
  * 2FA function wraps some secure functions like financial authorisations

This is all internally developed with a little bit of C for the security 
service and client end DLL.  We might dabble with Okta integration which 
is already in use at the site.   I am also considering an architecture 
written in OpenROAD entirely and using DB events to sent the 
authorisation messages.

Paul



On 29/08/2021 5:53 pm, Steve wrote:
> Hi folks
>
> Is using an Installation Password considered less secure, versus say DBMS authentication, when connecting to a remote Ingres installation?
>
> To give some context, I am thinking in terms of a cloud environment where Ingres installations can be spun up and down willy nilly. By spun up, I mean where Ingres is installed and started on a new server instance with the press of a button (well, that’s the theory).
>
> I thought DBMS authentication maybe more secure for connecting to a remote instance - presumably each user is prompted for their password when connecting. However, this would require the newly created Ingres installation to have the user information in order to authenticate the user.
>
> Also, this ignores the fact that the cloud provider will have their own layer of security.
>
> Any thoughts (apart from don’t over think it)?
>
> Thanks
> Steve
> _______________________________________________
> Info-ingres mailing list
> Info-ingres at lists.planetingres.org
> https://lists.planetingres.org/mailman/listinfo/info-ingres
-- 
Paul White
Shift Seven Solutions
*m: 0414681799*
p: 0754482137
e: paul.white at shift7solutions.com.au
w: https://www.shift7solutions.com.au
International: +61414681799
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.planetingres.org/pipermail/info-ingres/attachments/20210830/76b1de00/attachment.html>