1. Pascal Phan
  2. PowerServer
  3. Tuesday, 12 March 2024 20:01 PM UTC

This question is about the Password Expiration Dialog Box in Oracle and I am using PB2022 R2 (Build 2828) 

In PowerBuilder (PB) with the parameter:

SQLCA.DBParm    = "PWDialog=1"

If the User's Password expired, PB will display:

Whereas PowerServer (PS)  display nothing!

I put the MessageBox after the Connection Using SQLCA in the code 

 

SQLCA.DBParm    = "PWDialog=1"

CONNECT USING SQLCA;

// check for database connection info

MessageBox('Connection Info', 'Code:' + String(SQLCA.SQLDBCODE) + CHAR(13) + CHAR(10) + 'Message:' + SQLCA.SQLERRText )

And in PS display:

The SQLDBCODE is: -1

But in PB:

The SQLDBCODE is: 28001 plus the Password Expiration Dialog Box is display. 

This is bad in PS because User with expired Password cannot do anything unless someone else login successful to correct it.

Can someone help? 

Thanks

 

 

 

 

 

 

 

 

 

 

Francisco Martinez @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 12 March 2024 21:25 PM UTC
  2. PowerServer
  3. # 1

Here's the list of the supported DBParm properties: https://docs.appeon.com/ps2022r2/DBParm.html 

The documentation states that elements not listed on that page are not supported.

 

Regards,
Francisco

Comment
  1. Pascal Phan
  2. Wednesday, 13 March 2024 14:02 PM UTC
This DBParm property was supported in PowerBuilder and was important for User to change Password when expired. It should be carry on in PowerServer.
  1. Helpful
  1. Francisco Martinez @Appeon
  2. Wednesday, 13 March 2024 14:14 PM UTC
You're more than welcome to propose that support is added to that DB Parm on an enhancement request: https://www.appeon.com/standardsupport/search



This will make the product team aware that there's demand for the feature and might consider it for future development.
  1. Helpful
There are no comments made yet.
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Tuesday, 12 March 2024 20:36 PM UTC
  2. PowerServer
  3. # 2

Powerserver is much more limited in the supported dbparm parameters you can use.

You'll have to code a little window yourself to allow the user to change the pwd when expired error comes up.

Comment
  1. Pascal Phan
  2. Wednesday, 13 March 2024 14:08 PM UTC
I did create a Password changing dialog box but if the User could not login nothing can be done. The other solution is to re-login as DBA with hardcode Username and Password inside the App but this method is violate security.
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.