Supressing Password Change Requirement

[Former Member]

All,

I have come across a situation where I need to supress the requirement for a password change on a dialog user.

Our system parameters are set that the passwords for dialog users must be changed after 30 days.

I do not want to amend this setting however, for a specific user used for BW information broadcasting, the user's password should not be changed.

Unfortunately, the user needs to remain as a dialog user since it requires a direct logon to the system as part of the information broadcasting process.

Can the password reset requirement be supressed for a specific user?

Regards,

Simon

[Former Member]

Hi,

I don't know if this is applicable in your situation but if you make user as service user.

It won't ask for password change.

hope this helps

[Former Member]

The response posted was the same as the previous post.........................

Edited by: S Morar on Jul 11, 2008 10:59 AM

[jurjen_heeck]

OP clearly stated that his user needs to be dialog, so suggesting a usertype change is not going to help.

I do not know of any workarounds myself. (but am still curious)

[Former Member]

>

> OP clearly stated that his user needs to be dialog, so suggesting a usertype change is not going to help.
> I do not know of any workarounds myself. (but am still curious)

Though OP might not clearly have differentiated between "dialog capable user" and "dialog type user". Dialog type user would imply that the type is hardcoded, which is questionable...

A possible solution which might work, is not to save any UID and logon data into the connection and specify the "current user" flag. In this case, the current real dialog user (the person) will need a user ID in the target system, and will be prompted for a password to open the connection to it and authenticating themselves to do this.

Having said that, I have heard of scenarios in BW where the UID is entered in customizing, and only one UID can be entered. If that one must be dialog capable (or even must be a dialog type), then restricting it's authorizations to the bare minimum is important...

Cheers,

Julius

[Former Member]

Hi Simon,

There isn't much you can do if it's a dialog user. It has been done in the past where a change to the logon routine has made but that involves major changes, some lower than just the ABAP layer.

An alternative would be to ensure that the user only logs onto an app server with the parameter set to something like 5000 days (overrides the DEFAULT param value where pwd expiration is usually set). Having a specific app server for that could be overkill though & there are the usual risks with having an app server without standard settings.

Cheers & good luck!

Alex

[Former Member]

Having read the responses, as suspected, it appears that the best solution would be to try not to use Dialog users for this process.

[Former Member]

>

> Having read the responses, as suspected, it appears that the best solution would be to try not to use Dialog users for this process.

Yes, that is of course also a (better) better solution => to keep the connection Dialog-free and restrict it's authorizations such that it cannot administrate itself...

Cheers,

Julius