Sybase Password changes within Bus Obj

security Supervisor (4.x - 6.x)
1

Hello Group;

Sybase release 11, Windows 95, BO 4.1.2.

I’ve been working with our DBA’s to try to find a way to allow Bus Obj to initiate a password change via the Sybase stored procedure (“sp_password”) once the user is informed that their Sybase Password has expired.

BO Tech support indicated that they do not support stored procedures that do not return data. With that in mind, we have modified the “sp_password” function to return a “pass/fail” query response to eliminate the “No data to fetch” error.

We’ve hit a stumbling block. The procedure works great if you change your password before it expires. However after it has expired BO will not allow you to execute any SQL, procedure, universe, etc. Sybase itself (in Sybase via ISQL & not via BO) sends back an error Msg. #4022 telling you that your password has expired and logs you in, However you are only allowed to change your password at that point BO receives the message and must believe that the connection did not work so it will not allow you to open a free-hand SQL window, Stored Procedure, etc. So although Sybase has let you in, BO seems to have shut the door.

Unfortunately BO also does not pick up the messages that come back telling you your password will expire in x days when you log in, so you have no way of knowing that your password will be expiring soon. Most likely users will find out that their password has expired by running a query only to have it come back and tell them their password is expired and then it’s too late to do anything.

One (of several) suggestions that we came up with follows:

Write a simple GUI app to simply reset passwords. Once BO tells you that your password has expired you could exit BO, execute the GUI app and change your password and proceed in BO.

We’re still looking for a more elegant way, within BO to handle this.

Your input/ideas are appreciated.

Bruce Hinrichs
Information Warehouse Analyst
Schneider National, Inc.
Green Bay, WI USA
HinrichsB@Schneider.Com
(920) 592-2098

Listserv Archives (BOB member since 2002-06-25)

2

To expand upon your own suggestion, how about creating the GUI app with ReportScript, Map the script to the Business Objects Script Toolbar (choose Tools->Options->ReportScript to map the script to 1 of 5 toolbar buttons), and then make the scripting toolbar display by default (for ease of access). This will allow you to keep you solution inside the BO domain. I don’t think the scripting toolbar is the prettiest, but perhaps you may find this a convenient enhancement to your GUI App.

Hope that helps.

Don May
maydp@pweh.com

From: Hinrichs, Bruce[SMTP:HINRICHSB@SCHNEIDER.COM]
Sent: Tuesday, June 23, 1998 1:10 PM

Hello Group;

Sybase release 11, Windows 95, BO 4.1.2.

I’ve been working with our DBA’s to try to find a way to allow Bus Obj to
initiate a password change via the Sybase stored procedure (“sp_password”)
once the user is informed that their Sybase Password has expired.

BO Tech support indicated that they do not support stored procedures that do
not return data. With that in mind, we have modified the “sp_password” function to return a “pass/fail” query response to eliminate the “No data to
fetch” error.

We’ve hit a stumbling block. The procedure works great if you change your
password before it expires. However after it has expired BO will not allow
you to execute any SQL, procedure, universe, etc. Sybase itself (in Sybase
via ISQL & not via BO) sends back an error Msg. #4022 telling you that your
password has expired and logs you in, However you are only allowed to change
your password at that point BO receives the message and must believe that
the connection did not work so it will not allow you to open a free-hand SQL
window, Stored Procedure, etc. So although Sybase has let you in, BO seems
to have shut the door.

Unfortunately BO also does not pick up the messages that come back telling
you your password will expire in x days when you log in, so you have no way
of knowing that your password will be expiring soon. Most likely users will
find out that their password has expired by running a query only to have it
come back and tell them their password is expired and then it’s too late to
do anything.

One (of several) suggestions that we came up with follows:

Write a simple GUI app to simply reset passwords. Once BO tells you that
your password has expired you could exit BO, execute the GUI app and change
your password and proceed in BO.

We’re still looking for a more elegant way, within BO to handle this.

Your input/ideas are appreciated.

Bruce Hinrichs
Information Warehouse Analyst
Schneider National, Inc.
Green Bay, WI USA
HinrichsB@Schneider.Com
(920) 592-2098

Listserv Archives (BOB member since 2002-06-25)

3

Date: Wed, 24 Jun 1998 13:54:54 +0200

Hello

Von: Hinrichs, Bruce[SMTP:HINRICHSB@SCHNEIDER.COM] Betreff: Sybase Password changes within Bus Obj

Unfortunately BO also does not pick up the messages that come back telling you your password will expire in x days when you log in, so you have no way
of knowing that your password will be expiring soon. Most likely users will
find out that their password has expired by running a query only to have it
come back and tell them their password is expired and then it’s too late to
do anything.

I don’t know Sybase, so no complete solution here.

There must be information onm expiration date available in Sybase. Why not have a report that checks the date and informs the user? Wouldn’t it be possible to have the report run automatically at BO logon?

Just a thought…

Ryszard Mikke

Sorry if you can’t see the subject. Something breaks my headers. The subject is at the beginning of message body. --==> Hiroshima’45 Tschernobyl’86 Windows’95 <==-- R.Mikke@pl.vwfsag.de

Listserv Archives (BOB member since 2002-06-25)