You are not allowed to change your password. Please contact your system administrator.

[skinfrakkijm]

PassCore Server

• OS: Windows 2019

• Provider: [Active Directory | LDAP]

• Settings file (without sensitive information):

  "AppSettings": { // The following options for AD Provider (remove if you don't use this Provider) "UseAutomaticContext": true, // Set true to allow PassCore to reset password using the same credentials, or false if you will fill the credentials below "RestrictedADGroups": [ "Administrators", "Domain Admins", "Enterprise Admins" ], // Set the AD groups to restrict the use of PassCore "AllowedADGroups": [], // Set the AD Groups to allow PassCore, if the array is empty all the groups no-restricted above are allowed "IdTypeForUser": "UPN", // Possible values are "DN", "GUID", "Name", "SAM", "SID" and "UPN" (Default UPN) "UpdateLastPassword": false, // Set true to allow PassCore to update the last password timestamp // The following options are for LDAP Provider (remove if you don't use this Provider) "LdapSearchBase": "ou=users,dc=localdomain,dc=local", "LdapSecureSocketLayer": false, // Default for AD is true when using LDAPS 636 "LdapStartTls": false, // Default for AD is true when using LDAP 389 "LdapChangePasswordWithDelAdd": true, "LdapSearchFilter": "(sAMAccountName={Username})", // Another value: "(&(objectClass=person)(cn={Username}))" // General options (valid for both providers) "LdapHostnames": [ "" ], // Set your hostname(s) "LdapPort": 389, // Default for AD is 389, for LDAPS 636 "LdapUsername": "Administrator", // Set the username or distinguish name (DN) to bind the LDAP server "LdapPassword": "password", // Set the password for the username "DefaultDomain": "localdomain.local" // Set your default AD domain here, or non "@" logins will not work! Use empty value to allow user to set the domain. This option is ONLY available with UPN. },

• Log file (without sensitive information):

Describe the bug A clear and concise description of what the bug is.

Note: If you want to report an issue of passcorepro, please use the proper bug report form at https://store.unosquare.com/passcorepro

To Reproduce Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior A clear and concise description of what you expected to happen.

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context Add any other context about the problem here.

[simonai1254]

Hi

I guess here is missing some description, but for this error the thing that should be looked at in detail is the following configuration section:

"RestrictedADGroups": [
"Administrators",
"Domain Admins",
"Enterprise Admins"
], 

As soon as the user trying to change it's password is in one of these groups, the password change will fail.

Best regards Simon

[JoopIdema]

Just use version 3.61. Problem solved.

[simonai1254]

Why use such an old version? And 4.2.3 should work as well...

[makuc]

Same problem. Though to me, the provided binaries for version 4.2.4 didn't give me this error (I was overwhelmed with errors even though password was successfully changed -same issues as everyone else) and I saw that the error has been fixed, but the binaries hasn't been updated. So I went and rebuild it, having this problem since. Now installed v4.2.3 nad it works for now (though too bad about the .NET Core version).

[theQ23]

Same problem. Though to me, the provided binaries for version 4.2.4 didn't give me this error (I was overwhelmed with errors even though password was successfully changed -same issues as everyone else) and I saw that the error has been fixed, but the binaries hasn't been updated. So I went and rebuild it, having this problem since. Now installed v4.2.3 nad it works for now (though too bad about the .NET Core version).

Same here v4.2.3 fix all my issues including this one