You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When system is Locked, CPUS_UNLOCK_WORKSTATION in a Custom Credential Provider, DomainPassword Expiry Scenario is not working and not displaying Password change UI.
#10
Open
Mahaboob-Aslam opened this issue
Jun 22, 2021
· 0 comments
Hi,
I am writing a Custom Windows Credential Provider using C++ on Windows 10, where I have implemented the domain password expiry in my code and I am able to change the Domain password looking into this blog. How can I handle password expiry in the credential provider?
But there is one scenario, where in LOCK condition, CPUS_UNLOCK_WORKSTATION_condition, I am not able to load the Change Password UI for domain password expiry.
I am not able to load these fields. these APIs are failing to load fields OldPasswordText, OldPassword, NewPasswordText, NewPassword, ConfirmPasswordText and ConfirmPassword and Submitbutton.
I am calling this function from Credential :: Initialize().
I am calling Initialize() function from ReportResult()
below lines of code are from logfiles, which I am providing for reference.
Initialize() FAILED SFI_OLDPASSWORD_TEXT: 183 where 183 is the value, I am getting from GetLastError()
Initialize() FAILED SFI_OLDPASSWORD: 183
Initialize() FAILED SFI_OLDPASSWORD: 183
Initialize() FAILED SFI_NEWPASSWORD_TEXT: 183
Initialize() FAILED SFI_NEWPASSWORD_TEXT: 183
Initialize() FAILED SFI_NEWPASSWORD: 183
Initialize() FAILED SFI_CONFPASSWORD_TEXT: 183
Initialize() FAILED SFI_CONFPASSWORD: 183
Initialize() FAILED SFI_SUBMIT_BUTTON: 183
Help in resolving the issue, if i am doing anything wrong.
Regards
Aslam
The text was updated successfully, but these errors were encountered:
Mahaboob-Aslam
changed the title
When system is Locked CPUS_UNLOCK_WORKSTATION in a Custom Credential Provider Password Expiry Scenario is not working and not displaying Password change UI.
When system is Locked, CPUS_UNLOCK_WORKSTATION in a Custom Credential Provider, Password Expiry Scenario is not working and not displaying Password change UI.
Jun 22, 2021
Mahaboob-Aslam
changed the title
When system is Locked, CPUS_UNLOCK_WORKSTATION in a Custom Credential Provider, Password Expiry Scenario is not working and not displaying Password change UI.
When system is Locked, CPUS_UNLOCK_WORKSTATION in a Custom Credential Provider, DomainPassword Expiry Scenario is not working and not displaying Password change UI.
Jun 23, 2021
Hi,
I am writing a Custom Windows Credential Provider using C++ on Windows 10, where I have implemented the domain password expiry in my code and I am able to change the Domain password looking into this blog. How can I handle password expiry in the credential provider?
But there is one scenario, where in LOCK condition, CPUS_UNLOCK_WORKSTATION_condition, I am not able to load the Change Password UI for domain password expiry.
With this following code below:
for the above two statements, the code works fine and it hides the field components for Username and Passwords.
And I am facing problems for the below lines of code statements:
I am not able to load these fields. these APIs are failing to load fields OldPasswordText, OldPassword, NewPasswordText, NewPassword, ConfirmPasswordText and ConfirmPassword and Submitbutton.
I am calling this function from Credential :: Initialize().
I am calling Initialize() function from ReportResult()
below lines of code are from logfiles, which I am providing for reference.
Initialize() FAILED SFI_OLDPASSWORD_TEXT: 183 where 183 is the value, I am getting from GetLastError()
Initialize() FAILED SFI_OLDPASSWORD: 183
Initialize() FAILED SFI_OLDPASSWORD: 183
Initialize() FAILED SFI_NEWPASSWORD_TEXT: 183
Initialize() FAILED SFI_NEWPASSWORD_TEXT: 183
Initialize() FAILED SFI_NEWPASSWORD: 183
Initialize() FAILED SFI_CONFPASSWORD_TEXT: 183
Initialize() FAILED SFI_CONFPASSWORD: 183
Initialize() FAILED SFI_SUBMIT_BUTTON: 183
Help in resolving the issue, if i am doing anything wrong.
Regards
Aslam
The text was updated successfully, but these errors were encountered: