Number of days before user must change password.

Hi,
I understand how does this Essbase server setting work:
Essbase Server Properties - Security Tab
"Number of days before user must change password"
But my question is:
Does anyone know how "to mark" certain group of Users (mainly system admin accounts) - that this setting will not force periodical passoword change for "marked" users ?
Any ideas ?
Br, ripasso

There are a couple of things you could do to circumnavigate this all or nothing option.
You could write a maxl statement that would update the user profile to force the user to change their password e.g.
alter user Fiona set password_reset_days immediate;
I would write a program using the API that lists all users in the group and then dynamically create the maxl script that uses the statement above.
If you can not use the API then I guess you could do a maxl only solution (using display user command) and do some text file manipulation in perl (or another scripting language).
There are probably more solutions/ideas out there.

Similar Messages

Number of days before user needs to change password

If I enter a value for "Number of days before user needs to change password" will that effect both user and supervisor accounts or just user accounts? I have a supervisor account that we use for a lot of processes and do not want it to expire. However, our corporate security policy is to have user passwords expire at least every 90 days. Has anyone faced this before? Thanks, Mburkett

mburkett, Version 7.X has the external authentication option. The integration with active directory is very easy and can be configured in a few minutes. However, if your Essbase user names are different than MSAD user names, you would have to replace all Essbase users with their domain ID in order to use external authentication. If the user names are the same, it is only a matter of changing the flag to use the external AD password, rather then the Essbase password. If you are not using Hyperion HUB, you should install it prior to implementing External Authentication. I don't know the details of your custom job scheduler, but if it is based on ESSCMD, I dont see why it would not continue to work with an upgraded version. Good Luck, Chris

TMG 2010 publishing Exchange 2010 OWA cannot change password if user must change password at first logon is set

Hi,
I have an odd issue whereby if I set "user must change password" on an AD account, the end user cannot logon, they're simply taken back to the OWA login page as if their password is incorrect.
My setup is as follows:
outer TMG -- uses a listener for email.contoso.com and is configured for no authentication.This uses a publishing rule to publish the inner TMG server. This server is not a domain member.
inner TMG - uses a listener for email.contoso.com and is configured for NLTM\kerberos negotiation with forms authentication (Windows Active Directory). This server is a domain member and use a publishing rule to publish the internal CAS. Allow users to change
password is selected in the publishing rules.
Exchange 2010 SP1 - uses integrated windows and basic authentication. Has the appropriate registry key configured to allow users to change their AD password on first logon.
I've registered an snp for "http/email.contoso.com mailserver-dc1", all SSL certificates being used are valid and my configuration used to allow users to login and change their password with "user must change password on first login"
set in AD.
If I launch a web browser on an internal server and point it to email.contoso.com I'm immediately presented with a generic Windows authentication request (similar to what's seen in ADFS) rather than the standard OWA page. No matter what I do, I cannot login
and change my password using the correct URL. However if I point my browser at
http://192.168.4.10/owa I'm prompted to login and I can change my password using the sam credentials.
The only recent changes made are:
- Disabling SSL 3.0 and enabling TLS (http://www.isaserver.org/articles-tutorials/configuration-security/improving-ssl-security-forefront-threat-management-gateway-tmg-2010-published-web-sites.html)
- Replacing the TMG listener certificates so that they now use SHA2 rather than SHA2 (certificates are trusted on each TMG server)
Looking on the outer TMG and the DC logs I can see schannel errors which I believe are related to the problem. TMG monitoring also shows "Failed connection attempt: 1907 The user'spassword must be changed before logging on for the first time"
I've checked that my inner TMG and DC are using the same certificate for server authentication and gone through this guide:
http://blogs.technet.com/b/keithab/archive/2012/02/29/setting-up-and-troubleshooting-ldaps-authentication-in-forefront-tmg-2010.aspx
If I try to use ldp.exe on the inner TMG, I get the error in the pic below
Thanks
IT Support/Everything

Hi,
You could try to analyze the TMG tracing and try the troubleshoot steps in the blog below.
TMG 2010 – FBA, troubleshooting the change password feature
http://blogs.technet.com/b/isablog/archive/2012/05/07/tmg-2010-fba-troubleshooting-the-change-password-feature.aspx
Best Regards,
Joyce

Windows 2008 Terminal Server "user must change password at next logon" problem with Windows 7 client.

Hi,
I have a fully patched Windows 2008 SP2 Terminal Server and a fully patched Windows 7 client.
I have logged into the Windows 2008 SP2 Terminal Server server with a test account via RDC before.
When I try to log in via RDC to the 2008 TS with a test account which has been marked with the setting "User must change password at next logon" I get the RDC message "You must change your password before logging on the first time. For assistance, contact your system administrator or technical support." I need to force the user to change their password once it has been issued, any ideas on how this can be done?
Thanks,
Dan

This does not resolve my issue all the way. I'm having the same problem; When i'm "deploying" users, i always want the users to set their own passwords. Ok, so I then set the auth mode to "RDP Security layer". It seemed to work fine, and it does for that
special purpose.
Just like Daniel, my clients are connecting to our terminal server from several/different "customer-domains" So, they can't logon locally(on their local computer) and change their password, it has to be done THROUGH the terminal server.
But if I turn on RDP Security Layer, users can't use remoteapp through tsgw they only get: "Your Remote Desktop Connection Failed because the remote computer cannot be authenticated" Any ideas?
Also, our terminal servers is round robin based in a farm. So users connect to: tsfarm.domain.com(yes, public a-record which resolves to two internal adresses) This is because, we're using a wilcard *.domain.com as SSL certificate.
But, when i'm using this, our clients sometimes get double auth when they login. I only get the double auth when tsfarm.domain.com resolves to server A, but the session broker wants the user to be on server B.(load balancing)
This does not occur when SSL is enforced, any ideas?

OIM AD Integration - 'User must change password at next logon'

Hi,
These are the issues in OIM AD integration that we are stuck up on:
Issue:
1. When OIM Admin resets the password for User1 in OIM, the password is propagated to AD but the ‘User must change password at next logon’ attribute is not updated in AD. As a result, if the User1 logs into AD account (i.e. computer), there is no prompt to change the password.
2. When AD Admin resets the password for User1 in AD and checks the ‘User must change password at next logon’ flag, the password is propagated to OIM but the ‘obpasswordchangeflag’ attribute (of oblixPersonPwdPolicy class) is not updated in OID. As a result, if the User1 logs into OIM account, there is no prompt to change the password.
Research:
1. For case 1 above: When OIM Admin resets the password for User1, the ‘User must change password at next logon’ attribute on the AD process form itself is not getting updated. So the AD Connector doesn’t propagate the attribute to AD.
2. For case 2 above: When the AD Admin resets the password for User1 in AD, the AD Password Sync connector only sends the password to OIM and not other attribute. So, there is no way to fetch the ‘User must change password at next logon’ attribute and then copy it into ‘obpasswordchangeflag’ attribute in OID.
Environment Details:
1. OIM-OAM-OAAM 11.1.1.5 BP02 integrated using OVD-OID 11.1.1.5
2. AD on WIN 2008 R2.
3. OIM AD Connector 9.1.1.7.2
4. AD Password Sync Connector 9.1.1.5
Any help would be highly appreciated!
Thanks,
Kulesh...

Thanks for your reply again.
I did not get you completely here. Can you please elaborate on the "process task on the AD Process which passes along the USR_PWD_MUST_CHANGE and immediately sets it to 0 this should work". How many total additional tasks would be needed here?
what all targets are you provisioning the password to?
- AD and OID (through LDAPSYNC)
where are end users allowed to change their passwords on (OIM,AD....??)
- Both OIM and AD.
Where can admins change the passwords?
- Currently they use ARS for such purposes but this is something we need to clearly define. The thing is, they use ARS for whole lot of purposes and we can't dictate/restrict them to use OIM only for password resets. So they may use ARS or OIM.
What do you suggest?
Edited by: Kulesh Kane on Nov 8, 2012 11:43 AM

User must change password at next logon?

Hello,
We have an XMII / LDAP connection to AD. (Both read and write). But when ever we set a user in our AD to change password at next logon, they get block from logging into Xmii.
The funny part about this is if we do the following:
1: User login into Xmii
2: Administratator on AD controller, sets the flag "User must change password on next logon"
3: User selects Logout.
Now the user gets promt of changing his/her password.
Anyway to fix this?

Well we have some clients that doesn't use the same login to MII and for their workstation.
Basicly i want so whenever i set the flag "User must change password at nextlogon" in AD, I want MII to see that and make the user change his or her password in the portal.

User must change password after reset?

I am looking at the password policy settings and am wondering what "User must change password after reset� actually does. I turned it on. I tried changing some passwords in an ldap client and didnt get any messages or errors after authn again. And I didnt see a special attribute in the persons entry. Any clues?

When the flag is enabled and the password is changed by "cn=directory manager", the next time the user authenticate, the server returns the Password Expired Control (with a Success code) and all requests other than modify of userPassword are rejected.

"user must change password at next logon" flag for multiple users

2008 R2 domain with a couple of 2012 R2 DCs.
john.user is in the Users OU. if I right-click john.user, choose properties, go to the account tab, and check "user must change password at next logon," the next time john.user tries to log in, he gets prompted to change his password. also the
powershell command
get-aduser -filter * -Properties * | ? name -like "*john.user*" | select name,pwdlastset
shows that john.user's pwdlastset is 0. all of this is as expected.
but if I highlight every account in the Users OU, right-click, properties, Account, "user must change password at next logon," it appears that nothing whatsoever happens. john.user doesn't get prompted to change his password at his next
logon, and his pwdlastset is something like 130622757432306111.
is this the expected behavior? why are the Account tab and/or the "change password at next logon" box available to me when selecting multiple users if they aren't meant to work?

ah. thank you sir. *two* checkboxes. *two.* of course.
I had enough OUs under my Users OU that I just used powershell to catch them all at once:
$enabledusers = get-aduser -filter * -SearchBase "ou=users,dc=domain,dc=local" -Properties distinguishedname,pwdlastset |
    where {$_.enabled -eq "true" -and $_.distinguishedname -notlike "*ou=service accounts*"}
foreach($enableduser in $enabledusers) {
    $enableduser.pwdlastset = 0
    Set-ADUser -instance $enableduser

Exchange 2013 OWA user must change password at next logon not working

Hi,
I have installed Exchange 2013 on Windows 2012 Server. I create users in ECP and select "user must change password at next logon" option. When newly created user logs in, the OWA page doesn't prompt for password change and just throws error "The
user name or password you entered isn't correct. Try entering it again"
I have enabled Change Password feature in CAS server, but still not working.
Any answers, suggestions would be great help
Regards
Sunil

Hi Sunil,
Have you tried as Martina said and does it work?
If not, please try to set the Minimum Password Age to 1 according to link below. I found some threads which are similar to yours and were solved by this way in Exchange 2013 environment.
http://support.microsoft.com/kb/827614
And for further troubleshooting, please create a new user with "user must change password at next logon" option checked and see if he can log on domain-joined PC.
In addition, please check the event log to see if there is any related error message.
Regards,
Rebecca

Network account - Having "user must change password at nex logon checked" - does not allow user to login

Hi,
We have several SharePoint 2013 sites which, when the option called "User must change password at next logon" is checked on a user's Active Directory account, the user is not allowed to login to the SharePoint site. Is this something that needs
to be changed on the SharePoint end to resolve?
thanks,
Sherazad.
Sherazad

You need to look at a different solution that allows this, e.g. home-grown solution, 3rd party, and I believe Forefront Identity Manager can also accomplish this task. There are quite a few self-service password management solutions out there. Search on
that term, and you should be able to find something that works for you.
Trevor Seward
Follow or contact me at...
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Be careful of "Prompt user to change password before expiration" policy -- it's counting the days wrong!!

After several tests, I'm pretty sure that the policy "Interactive logon: Prompt user to change password before expiration" is counting the wrong days. (Note: this policy is in Windows Settings > Security Settings > Local Policies > Security
Options) So I think I should post this in the forum in the hope that it could be helpful to others in the same case as me, esp if the policy is pushed out as a domain-wide policy.
First, the context of the test, ie domain-wide policy settings:
1. Password minimum age = 2 days
2. Password maximum age = 4 days
3. Prompt user to change password before expiration = 2 days
If everything is going fine, users will be asked to change password when it is changeable (ie it has reached the minimum age). However, it turns out that users are prompted BEFORE they can change password. Look at the image below that I got in
Win7:
(In WinXP, we have similar prompt when user has just logged in)
Look at the clock: it's 13:16 (04/12/2013). Then look at the DOS window in which I ran the "net user /domain" command and read the line "Password expires": it's shown
06/12/2013 18:09:04.
A little math would tell me that if users are prompted to change password *2 days* before expiration, the dialog will appear
ONLY AFTER 04/12/2013 18:09:04. But since the prompt is shown at 13:16 (ie well before 18:09), that mean the "prompt user...." policy makes mistakes in calculating the moment to show the prompt.
In other words, if we have the policy set like this:
Prompt user to change password before expiration =
N days
The prompt will actually appear from N+1 days before expiration.
I would consider this as a bug, but I also suppose it's hard to make Microsoft fix it. So that's why I make this post to warn others. In my case, I have received several calls from users complaining that they were prompted to change password
but their new passwords were always refused and they had no idea what went wrong. And it took me a lot of effort to sort out what really went wrong. And in order to work around this stupid bug, I have to change the "Prompt user...." policy
to N-1 days (before expiration) instead of N days previously.
Hope this help

Hi,
Based on my research, you are right that the prompt policy is implemented by date, which is by design.
“Set
Interactive logon: Prompt user to change password before expiration to 5 days. When their password expiration
date is 5 or fewer days away, users will see a dialog box each time they log on to the domain”, I quoted this sentence from the article below:
Interactive logon: Prompt user to change password before expiration
http://technet.microsoft.com/en-us/library/jj852243.aspx
The problem is consistency! For Minimum/Maximum password age properties, they are also defined for
days as well. But for them, days are exact days, ie a
multiple of exactly 24 hours. There is an "Explain" tab for every parameter, but even if you read them through, you can't tell if day means strict multiple of 24 hours or loose definition of days. I'll leave the exercise to you to read
them if you like and spare me the article from your KB library.
As for the password minimum age part, what I mean is that is why users can’t not change their password within 2 days when the prompt appears before the changeable time.
Anyway, I agree with you that we need to be careful when we configure the password policy because the Prompt policy is not doing calculation by hours.
Miss, the 2 days is just a TEST EXAMPLE. Let's say it's
N days if you was unable to understand. I wouldn't change N days to N-1 days because of this stupid GUI bug. As I said earlier and let me repeat it once more,
Minimum password age = N days is a security policy and it is more important than the user prompt and no security officer with sane mind will change this.

RSOP: Interactive logon: Prompt user to change password before expiration

Hi,
I am trying to implement a GPO so that users are prompted to change their password 5 days before it expires. I have done this via -
Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options > Enabled
Interactive Logon: Prompt user to change password before expiration
Despite doing the above the GPO does not seem to be taking effect. I have run RSOP on my machine and a few users machines and can see that there is a red circle with an X next to
Interactive Logon: Prompt user to change password before expiration.
Below is my winlogon.log file but I am not really sure what I am supposed to be looking for. Can anyone help?
Make a local copy of \\**************.co.uk\sysvol\**************.co.uk\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Machine\Microsoft\Windows NT\SecEdit\GptTmpl.inf.
GPLinkSite GPO_INFO_FLAG_BACKGROUND )
Make a local copy of \\**************.co.uk\sysvol\**************.co.uk\Policies\{91EDC47D-AACF-4DFE-B044-5D29500CECBE}\Machine\Microsoft\Windows NT\SecEdit\GptTmpl.inf.
GPLinkDomain GPO_INFO_FLAG_BACKGROUND )
Make a local copy of \\**************.co.uk\SysVol\**************.co.uk\Policies\{DDE2DDB7-9802-415B-819E-1ADA496DC3E6}\Machine\Microsoft\Windows NT\SecEdit\GptTmpl.inf.
GPLinkDomain GPO_INFO_FLAG_BACKGROUND )
Make a local copy of \\**************.co.uk\sysvol\**************.co.uk\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Machine\Microsoft\Windows NT\SecEdit\GptTmpl.inf.
GPLinkDomain GPO_INFO_FLAG_BACKGROUND )
Make a local copy of \\**************.co.uk\SysVol\**************.co.uk\Policies\{6422C1A4-D958-4F4B-A8AA-EBACC567BD19}\Machine\Microsoft\Windows NT\SecEdit\GptTmpl.inf.
GPLinkOrganizationUnit GPO_INFO_FLAG_BACKGROUND )
No template is defined in GPO \\**************.co.uk\SysVol\**************.co.uk\Policies\{43F654AA-56D5-4F2C-B357-1AFEE03D37F2}\Machine.
Process GP template gpt00000.inf.
This is not the last GPO.
08 March 2015 23:06:35
Copy undo values to the merged policy.
----Un-initialize configuration engine...
Process GP template gpt00001.dom.
This is not the last GPO.
08 March 2015 23:06:36
----Un-initialize configuration engine...
Process GP template gpt00002.dom.
This is not the last GPO.
08 March 2015 23:06:36
----Un-initialize configuration engine...
Process GP template gpt00003.dom.
This is not the last GPO.
08 March 2015 23:06:36
----Un-initialize configuration engine...
Process GP template gpt00004.inf.
08 March 2015 23:06:36
----Configuration engine was initialized successfully.----
----Reading Configuration Template info...
----Configure User Rights...
Configure S-1-5-32-544.
Configure S-1-5-21-778002760-1239436532-1307212239-1002.
Configure S-1-5-21-778002760-1239436532-1307212239-1016.
Configure S-1-5-21-778002760-1239436532-1307212239-4078.
Configure S-1-5-21-778002760-1239436532-1307212239-512.
Configure S-1-5-21-778002760-1239436532-1307212239-500.
Configure S-1-5-21-778002760-1239436532-1307212239-513.
User Rights configuration was completed successfully.
----Configure Group Membership...
Configure **************\Local Admins for Users.
old memberof tattoo list: *S-1-5-32-555,*S-1-5-32-544,
object already member of Administrators.
object already member of Remote Desktop Users.
new memberof tattoo list: *S-1-5-32-555,*S-1-5-32-544,
Group Membership configuration was completed successfully.
----Configure Security Policy...
Configure password information.
Configure account force logoff information.
System Access configuration was completed successfully.
Configure machine\software\microsoft\windows nt\currentversion\winlogon\passwordexpirywarning.
Configure machine\software\microsoft\windows\currentversion\policies\system\enableinstallerdetection.
Configuration of Registry Values was completed successfully.
Audit/Log configuration was completed successfully.
----Configure available attachment engines...
Configuration of attachment engines was completed successfully.
----Un-initialize configuration engine...
this is the last GPO.
Make a local copy of \\**************.co.uk\sysvol\**************.co.uk\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Machine\Microsoft\Windows NT\SecEdit\GptTmpl.inf.
GPLinkSite GPO_INFO_FLAG_BACKGROUND )
Make a local copy of \\**************.co.uk\sysvol\**************.co.uk\Policies\{91EDC47D-AACF-4DFE-B044-5D29500CECBE}\Machine\Microsoft\Windows NT\SecEdit\GptTmpl.inf.
GPLinkDomain GPO_INFO_FLAG_BACKGROUND )
Make a local copy of \\**************.co.uk\SysVol\**************.co.uk\Policies\{DDE2DDB7-9802-415B-819E-1ADA496DC3E6}\Machine\Microsoft\Windows NT\SecEdit\GptTmpl.inf.
GPLinkDomain GPO_INFO_FLAG_BACKGROUND )
Make a local copy of \\**************.co.uk\sysvol\**************.co.uk\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Machine\Microsoft\Windows NT\SecEdit\GptTmpl.inf.
GPLinkDomain GPO_INFO_FLAG_BACKGROUND )
Make a local copy of \\**************.co.uk\SysVol\**************.co.uk\Policies\{6422C1A4-D958-4F4B-A8AA-EBACC567BD19}\Machine\Microsoft\Windows NT\SecEdit\GptTmpl.inf.
GPLinkOrganizationUnit GPO_INFO_FLAG_BACKGROUND )
No template is defined in GPO \\**************.co.uk\SysVol\**************.co.uk\Policies\{43F654AA-56D5-4F2C-B357-1AFEE03D37F2}\Machine.
Process GP template gpt00000.inf.
This is not the last GPO.
09 March 2015 16:26:51
Copy undo values to the merged policy.
----Un-initialize configuration engine...
Process GP template gpt00001.dom.
This is not the last GPO.
09 March 2015 16:26:51
----Un-initialize configuration engine...
Process GP template gpt00002.dom.
This is not the last GPO.
09 March 2015 16:26:51
----Un-initialize configuration engine...
Process GP template gpt00003.dom.
This is not the last GPO.
09 March 2015 16:26:51
----Un-initialize configuration engine...
Process GP template gpt00004.inf.
09 March 2015 16:26:51
----Configuration engine was initialized successfully.----
----Reading Configuration Template info...
----Configure User Rights...
Configure S-1-5-32-544.
Configure S-1-5-21-778002760-1239436532-1307212239-1002.
Configure S-1-5-21-778002760-1239436532-1307212239-1016.
Configure S-1-5-21-778002760-1239436532-1307212239-4078.
Configure S-1-5-21-778002760-1239436532-1307212239-512.
Configure S-1-5-21-778002760-1239436532-1307212239-500.
Configure S-1-5-21-778002760-1239436532-1307212239-513.
User Rights configuration was completed successfully.
----Configure Group Membership...
Configure **************\Local Admins for Users.
old memberof tattoo list: *S-1-5-32-555,*S-1-5-32-544,
object already member of Administrators.
object already member of Remote Desktop Users.
new memberof tattoo list: *S-1-5-32-555,*S-1-5-32-544,
Group Membership configuration was completed successfully.
----Configure Security Policy...
Configure password information.
Configure account force logoff information.
System Access configuration was completed successfully.
Configure machine\software\microsoft\windows nt\currentversion\winlogon\passwordexpirywarning.
Configure machine\software\microsoft\windows\currentversion\policies\system\enableinstallerdetection.
Configuration of Registry Values was completed successfully.
Audit/Log configuration was completed successfully.
----Configure available attachment engines...
Configuration of attachment engines was completed successfully.
----Un-initialize configuration engine...
this is the last GPO.
Jeet S

******UPDATE******
I think I have managed to get this working. I changed the source of the policy to a different GPO. I then did the following -
From a command prompt run gpupdate (without the force parameter)
Ran rsop.msc and checked the policy and this time there was no red circle with an X
Have done the same on a few users machines and it appears to apply successfully. I say this because when you go into the properties for the policy you see the following -
The policy XYZ was correctly applied
Just have to wait and see if it actually does what it says on the can.
Jeet S

How to Restrict users to change password

Hi All,
I would like to restrict user to change password only defined number of times in a day, Is it possible to do it through group policies.
Please note i am already aware of "Minimum Password age" feature, however i do not want to use it as the minimum value that i can set here is 1 day. I would like to restrict users based on password reset threshold e.g. User can reset his password
in a day only twice or thrice.
Thanx & Regards,
Wasim Parkar

If you want to limit the user to have his/her password changed for a specific number of time every day, I have to say
NO thats not possible. PSO's as other mentioned,can be used to have different password policies. Maybe you can set the msDS-MinimumPasswordAge
to 00:04:00:00 which is equal to 4 hours. It means every 4 hours a user will be able to change his/her password. So in each day a user can change the password 6 times, since a day is 24 hours.
Do not forget a day start from 00:00 AM up to 11:59 PM. So in a 9 to 5 job, a user may change the password 2-3 times.
Hope it helps.
Mahdi Tehrani Loves Powershell
Please kindly click on Propose As Answer or to mark this post as
and helpfull to other poeple.

User cannot change password option is automatically getting unchecked while giving domain admin rights

user cannot change password option is automatically getting unchecked while giving domain admin rights

Greetings!
"Domain Admins" falls into the category of protected groups and it is included in ADminSDHolder process. It is normal and was designed in order to prevent the modification to these privileged groups. More information on the link below:
AdminSDHolder, Protected Groups and SDPROP
Regards.
Mahdi Tehrani |
|
www.mahditehrani.ir
Please click on Propose As Answer or to mark this post as
and helpful for other people.
This posting is provided AS-IS with no warranties, and confers no rights.
How to query members of 'Local Administrators' group in all computers?

Create a user through the API and "Prompt user to change password after next login".

Using the Adobe Connect Interface, I can create a user and check the checkbox to "Prompt user to change password after next login".
Can I achieve the same result using the API? The principal-update action doesn't offer such an option and, as far as I can tell, there isn't another action to do so either.
Thank you.

You can achieve it as part of your application functionality, but not as a configuration option on WLS.

Number of days before user must change password.

Similar Messages

Maybe you are looking for