
PassCore is a very simple 1-page web application written in C#, using ASP.NET Core, Material UI (React Components), and Microsoft Directory Services (Default provider).
It allows users to change their Active Directory/LDAP password on their own, provided the user is not disabled.
You can check the wiki section for additional content related to development of this project.
PassCore has the following features:
Easily localizable (i.e. you can customize all of the strings in the UI -- see the section on Customization)
Supports reCAPTCHA
Has a built-in password meter
Has a password generator
Has a server-side password entropy meter
Responsive design that works on mobiles, tablets, and desktops.
Works with Windows/Linux servers.
You can use the Alpine Docker Builder image and then copy the assets over to an Alpine container. You can pass environment attributes directly into docker without modifying the appsettings.json
docker build --rm -t passcore .
docker run \
-e AppSettings__LdapHostnames__0='ad001.example.com' \
-e AppSettings__LdapHostnames__1='ad002.example.com' \
-e AppSettings__LdapPort='636' \
-e AppSettings__LdapUsername='CN=First Last,OU=Users,DC=example,DC=com' \
-it \
-p 80:80 \
passcore:latest
AppSettings__LdapUsername - Set the username or distinguish name (DN) to bind the LDAP server
AppSettings__LdapPassword - Set the password for the username
ClientSettings__Recaptcha__SiteKey - ReCAPTCHA public key: replace this! or leave empty if you don't need ReCAPTCHA
ClientSettings__Recaptcha__PrivateKey - ReCAPTCHA private key: replace this! or leave empty if you don't need ReCAPTCHA
NOTE: Docker image contains a build using the LDAP Provider (see below).
PassCore was created to use the Microsoft Active Directory Services provided by .NET Framework, but a new Provider using Novell LDAP Client can be used instead. This provider is the default when PassCore is running at Linux or macOS since Microsoft AD Services are NOT available.
The configuration of the LDAP Provider is slightly different. for example, the AutomaticContext is not available and you need to supply credentials.
Sometimes a simple set of checks and some custom logic is enough to rule out non-secure trivial passwords. Those checks are always performed locally. There are, however, many more unsafe passwords that cannot be ruled out programatically. For those cases there are no simple set of rules that could be used to check those passwords that should never be used: You either need a local DB with a list of banned passwords or use an external API service.
Here is where Pwned Password API comes into play. Pwned Passwords are more than half a billion passwords which have previously been exposed in different data breaches along the years. The use of this service is free and secure. You can read more about this service in Pwned Passwords overview
All server-side settings and client-side settings are stored in the /appsettings.json file.
The most relevant configuration entries are shown below. Make sure you make your changes to the appsettings.json file using a regular text editor like Visual Studio Code
PrivateKey entry and enter your private key within double quotes (")SiteKey entry and enter your Site Key within double quotes (")LanguageCode entry and enter one of the options listed here. By default this is set to enShowPasswordMeter entry and set it to true or false (without quotes)UsePasswordGeneration entry and set it to true or false (without quotes)PasswordEntropy entry and set it to a numeric value (without quotes) to set the entropy of the generated passwordMinimumScore entry and set it to a numeric value (without quotes) between 1 and 4, where 1 is a bit secure and 4 is the most secure. Set to 0, for deactivate the validation.RestrictedADGroups entry and add any groups that are sensitive. Accounts in these groups (directly or inherited) will not be able to change their password.DefaultDomain entry and set it to your default Active Directory domain. This should eliminate confusion about using e-mail domains / internal domain names. NOTE: if you are using a subdomain, and you have errors, please try using your top-level domain.http://mypasscore.com/?userName=someusernameIdTypeForUser it is possible to select one of six Attributes that will be used to search for the specifiv user.DistinguishedName or DNGloballyUniqueIdentifier or GUIDNameSamAccountName or SAMSecurityIdentifier or SIDUserPrincipalName or UPNTo run as a sub-application you need to modify the base href="/" value in the wwwroot/index.html file to be the base URL for PassCore. For example you might have PassCore setup at /PassCore so you would put
<base href="/PassCore/" />
PasswordChangeOptions in the /appsettings.json file. Here are some guidelines:
UseAutomaticContext is set to falseLdapUsername is set to an AD user with enough permissions to reset user passwordsLdapPassword is set to the correct password for the admin user mentioned abovedomain\\ or @domain. Only the username.Content type
Image
Digest
Size
44.3 MB
Last updated
over 6 years ago
docker pull defaultvalue/passcore