User ID and password

S

sengodan

New Member
Hi all,

I am planning to setup user Id and password for accessing procedure editor on windows side, since we refresh private box with production data. I don't want everybody to access the database directly and fetch the data rather it should prompt foruser Id & password.. how do i do that :awink:
 
As soon as you have one entry in the _User table the login dialog will pop up when you start the procedure editor ( or AppBuilder ... ). But you still need to disable blank userid access to the database because otherwise one could just escape the login dialog and will be able to work in the proceudre editor. You can do all this in the data administration tool ( admin menu / security / edit user list and disallow blank userid access ).

HTH, RealHeavyDude.
 
Hi Thanks for the informantion !!:) I need some more information on the same.. Like we have 10 databases to connect and we have set up windows shortcut keys to connect to progress editor which connect all the 10 databases using one single .pf which passes username and password. When trying to connect to all the database i require user to pass username and password once for connecting all the 10 database inorder to validate the user. Please suggest
 
High,

to dig deeper into the topic you need to tell on wich Progress/OpenEdge version you are running.

When you supply the username and password in Progress paramter file or on the command line or in a Windows shortcut you can't supply it in an encrypted form. Therefore I don't think it is a good idea to provide such sensitive information in that way.

I know that almost all of the application do the database connect from the parameter file supplied to the Progress executable. I don't think that is really a good idea: For one if the connect fails, your Progress/OpenEdge session will stop and you have no chance to handle a connection exception - an ugly Progress error message will pop up to the user. Secondly, you have no real choice for the authentification technique when the blank userid access to the database is disabled.

Therefore I prefer to do the connect with the CONNECT statement in the ABL session. This way you have much more freedom on handling exceptions and authenticate the Progress/OpenEdge sessions against connected databases. Be it the use of the Progress User table or the client principal object which is availbel for 10.0B+ (if I remember correctly).

HTH, RealHeavyDude.
 
You must log in or register to reply here.
Back
Top