Skip to content

A free open source IT asset/license management system

Added new strings

snipe4ad92657e095
diff --git a/resources/lang/en-US/admin/settings/general.php b/resources/lang/en-US/admin/settings/general.php
index a1e526e8a0..3e5743a537 100644
--- a/resources/lang/en-US/admin/settings/general.php
+++ b/resources/lang/en-US/admin/settings/general.php
@@ -95,6 +95,104 @@ return [
'label_logo_size' => 'Square logos look best - will be displayed in the top right of each asset label. ',
'laravel' => 'Laravel Version',
'ldap' => 'LDAP',
+ 'ldap_wizard' => [
+ 'step_connection' => 'Connection',
+ 'step_authscope' => 'Authenticate & Scope',
+ 'step_mapping' => 'Attribute Mapping',
+ 'step_sync' => 'Sync & Defaults',
+ 'step_authscope_help' => 'Provide the admin bind account used to connect, plus the base DN and filter that define where to look for users. Verification binds with these credentials and runs a search under the base DN to confirm both work together before you continue.',
+ 'combined' => [
+ 'success' => 'Bound as :user and found :count :entries under your base DN. Ready to map attributes.',
+ ],
+ 'step_connection_help' => 'Configure how to reach your LDAP or Active Directory server. Once saved, you can test the connection before moving on to bind credentials.',
+ 'ldap_uname_help' => 'The distinguished name (DN) or User Principal Name (UPN) of an admin service account that can search your directory. For Active Directory this is usually a UPN like <code>[email protected]</code>. For OpenLDAP and most other directories this is a full DN like <code>cn=admin,dc=example,dc=com</code>. Enter the entire path including the base DN portion, not just the account name.',
+ 'ldap_pword_help' => 'Leave blank to keep the previously-saved password.',
+ 'bind' => [
+ 'pword_decrypt_failed' => 'Could not decrypt the stored bind password. This usually means the app key changed since the password was saved. Enter the password again to fix.',
+ 'rejected' => 'The LDAP server rejected the bind (:error). Double-check the username and password.',
+ ],
+ 'ldap_basedn_help' => 'The distinguished name (DN) where the user search begins. Everything below this DN is in scope. Typically the OU or container that holds your synced users.',
+ 'ldap_filter_help' => 'LDAP filter expression used to narrow the search to synceable users. Omit the outer parentheses, they are wrapped automatically. Leave blank to accept all objects under the base DN, though this is rarely what you want.',
+ 'ldap_auth_filter_query_help' => 'How the LDAP query is built when authenticating a user login. Usually the login-attribute name followed by an equals sign, for example uid= or samaccountname=. This gets appended with the login username at auth time.',
+ 'search' => [
+ 'basedn_equals_binddn' => 'This base DN is the same as the bind account DN, which is a leaf entry (a single user, not a container). Set the base DN to the container that holds your users, usually one level up (for example dc=example,dc=com instead of cn=admin,dc=example,dc=com).',
+ 'bind_failed' => 'Could not bind to the LDAP server with the saved credentials to run the search (:error). Go back to the Bind Credentials step and re-verify.',
+ 'pword_decrypt_failed' => 'Could not decrypt the stored bind password. Go back to the Bind Credentials step and re-enter it.',
+ 'search_failed' => 'The search failed: :error',
+ 'no_results' => 'The search completed but returned zero results. Double-check your base DN and filter. You would sync zero users with this configuration.',
+ 'success' => 'The search returned :count matching :entries. Ready to configure how those user attributes map to local user fields.',
+ 'entries_one' => 'entry',
+ 'entries_other' => 'entries',
+ ],
+ 'step_mapping_help' => 'Specify which LDAP attributes hold each piece of user information. <strong>Always use the lower-case form of the attribute name.</strong> If your LDAP or AD shows the field as <code>displayName</code>, <code>givenName</code>, or <code>sAMAccountName</code>, enter <code>displayname</code>, <code>givenname</code>, or <code>samaccountname</code> here. Camel-case values fail to match on most servers and are the most common cause of "no fields sync" reports. Username and First Name are required. You can leave others blank if your directory does not carry that data or if you do not want to sync it.',
+ 'step_sync_help' => 'Final step: enable LDAP and pick the defaults to apply to newly-synced users. When the enable toggle is on and saved, LDAP is live, users can sign in with their directory credentials and admin sync jobs will start pulling accounts.',
+ 'sync' => [
+ 'save_and_enable' => 'Save & Enable LDAP',
+ 'save_and_finish' => 'Save & Finish',
+ 'ldap_pw_sync_label' => 'Sync passwords from LDAP',
+ 'no_default_group' => 'No default permissions group',
+ 'default_group_help' => 'Permissions group applied to newly-synced users. Choose "No default permissions group" to give them no automatic access. You can grant permissions per-user later.',
+ 'custom_forgot_pass_url_help' => 'When set, the Forgot Password link on the login page redirects here instead of triggering the built-in password reset flow. Useful when directory passwords are managed externally.',
+ ],
+ 'mapping' => [
+ 'sample_username_label' => 'Sample username to test',
+ 'sample_username_placeholder' => 'e.g. alice',
+ 'sample_username_help' => 'Enter a real LDAP username to fetch that user and preview what values would be synced using your current mapping.',
+ 'lookup_button' => 'Look up user',
+ 'no_sample' => 'Enter a sample username to preview attribute mapping.',
+ 'not_found' => 'No LDAP entry found for :username. Search filter used: ":filter" under base DN ":basedn". Double-check the Username Field mapping on this step, plus the base DN and filter on the Authenticate & Scope step. A common cause is pointing the base DN at a leaf entry (like the bind account itself) instead of the container that holds your users. Users usually live one level up, under an ou= or dc= container.',
+ 'multiple_found' => 'Found :count entries for :username. Your filter should narrow this to a single user. Search filter used: ":filter".',
+ 'found' => 'Found user :dn. Values below are what would be synced using your current attribute mapping.',
+ 'value_missing' => '(not present on LDAP entry)',
+ 'field_not_mapped' => '(no LDAP attribute configured)',
+ 'preview_snipe_field' => 'User field',
+ 'preview_ldap_attribute' => 'LDAP attribute',
+ 'preview_ldap_value' => 'Value from LDAP',
+ ],
+ 'save_and_next' => 'Save & Continue',
+ 'verifying' => 'Verifying…',
+ 'verifying_help' => 'Connecting to your LDAP server and verifying the settings you provided. This may take a few seconds if your server is slow to respond or takes time to negotiate TLS.',
+ 'placeholder' => 'This step is coming soon. Complete the earlier steps first, then check back once this section is implemented.',
+ 'progress_label' => 'LDAP setup progress',
+ 'step_of' => 'Step :num of :total',
+ 'state_complete' => 'completed',
+ 'state_current' => 'current step',
+ 'state_locked' => 'locked, complete the earlier steps to unlock',
+ 'locked_help' => 'Save the earlier steps before jumping to this one.',
+ 'confirm_discard' => 'You have unsaved changes on this step. Continue and discard them?',
+ 'disable_ldap_button' => 'Disable LDAP',
+ 'disable_ldap_modal_title' => 'Disable LDAP?',
+ 'confirm_disable_ldap' => 'Users who log in with LDAP will lose access until you re-enable it. Your existing configuration will be preserved.',
+ 'disabled_success' => 'LDAP has been disabled. Your configuration is still saved and can be re-enabled at any time by completing the wizard.',
+ 'done' => [
+ 'title' => 'LDAP is enabled',
+ 'intro' => 'Your directory is connected and users can now sign in with their LDAP credentials. Consider setting up a scheduled sync so new and updated users are pulled from your directory automatically.',
+ 'sync_heading' => 'Keep users in sync with your directory',
+ 'sync_intro' => 'User syncing is a separate step from authentication. Log-in works right now, but existing accounts are only refreshed when a sync runs. Pick the option that matches your host:',
+ 'sync_cron_title' => 'Linux, macOS, and other Unix-like hosts',
+ 'sync_cron_body' => 'Add this entry to the crontab of the web-server user (usually <code>www-data</code>). It runs the LDAP sync every hour:',
+ 'sync_windows_title' => 'Windows',
+ 'sync_windows_body' => 'Create a Scheduled Task that runs the command below every hour, with the working directory set to your installation path:',
+ 'sync_manual_title' => 'Run a one-off sync from the command line',
+ 'sync_manual_body' => 'Useful for the first sync or when troubleshooting. Run from your installation directory:',
+ 'back_to_settings' => 'Back to Settings',
+ ],
+ 'test' => [
+ 'connect_failed' => 'Could not complete an LDAP handshake with :server. The host may be unreachable, or the port may be open but not actually running an LDAP server. For example, "google.com:636" answers on port 636 but is not the LDAP endpoint. The correct hostname is "ldap.google.com". Double-check the hostname your LDAP/AD provider gave you.',
+ 'starttls_failed' => 'STARTTLS handshake failed: :error',
+ 'connected' => 'Successfully connected to :server.',
+ 'connected_no_anon' => 'Reached :server but the server rejected the anonymous connectivity check (:error). This is fine. Bind credentials are configured in the next step.',
+ 'dns_failed' => 'Could not resolve host ":host" via DNS. Check the spelling.',
+ 'private_ip_blocked' => 'Host ":host" resolves to :ip, which is on a private, loopback, or reserved IP range. Testing against internal IPs is blocked by default to prevent this instance from being used as a network probe. If your LDAP server legitimately lives on a private network, set TEST_ALLOW_PRIVATE_IPS=true in your .env.',
+ 'rate_limited' => 'Too many test attempts. Please wait :seconds seconds before testing again.',
+ ],
+ 'tls' => [
+ 'key_parse_failed' => 'This does not look like a valid PEM-encoded private key. It should begin with -----BEGIN … PRIVATE KEY----- and end with -----END … PRIVATE KEY-----.',
+ 'cert_parse_failed' => 'This does not look like a valid PEM-encoded certificate. It should begin with -----BEGIN CERTIFICATE----- and end with -----END CERTIFICATE-----.',
+ 'cert_expired' => 'This certificate expired on :date. Regenerate it before enabling client TLS authentication.',
+ 'pair_mismatch' => 'The private key does not correspond to the certificate above. Double-check that you pasted the matching pair.',
+ ],
+ ],
'ldap_default_group' => 'Default Permissions Group',
'ldap_default_group_info' => 'Select a group to assign to newly synced users. Remember that a user takes on the permissions of the group they are assigned.',
'no_default_group' => 'No Default Group',
@@ -105,11 +203,11 @@ return [
'ldap_integration' => 'LDAP Integration',
'ldap_settings' => 'LDAP Settings',
'ldap_client_tls_cert_help' => 'Client-Side TLS Certificate and Key for LDAP connections are usually only useful in Google Workspace configurations with "Secure LDAP." Both are required.',
- 'ldap_location' => 'LDAP Location Field',
+ 'ldap_location' => 'Location Field',
'ldap_location_help' => 'The LDAP Location field should be used if <strong>an OU is not being used in the Base Bind DN.</strong> Leave this blank if an OU search is being used.',
'ldap_login_test_help' => 'Enter a valid LDAP username and password from the base DN you specified above to test whether your LDAP login is configured correctly. YOU MUST SAVE YOUR UPDATED LDAP SETTINGS FIRST.',
'ldap_login_sync_help' => 'This only tests that LDAP can sync and that your fields are mapped correctly. If your LDAP Authentication query is not correct, users may still not be able to login. YOU MUST SAVE YOUR UPDATED LDAP SETTINGS FIRST.',
- 'ldap_manager' => 'LDAP Manager Field',
+ 'ldap_manager' => 'Manager Field',
'ldap_mapping_help' => 'If your fields are not syncing correctly, try using the <strong>lower-case version</strong> of the field names. Display Name (<code>displayName</code>) in your LDAP/AD should be mapped here as <code>displayname</code>, <code>givenName</code> should be <code>givenname</code>, <code>sAMAccountName</code> as <code>samaccountname</code>, etc. <a href="https://snipe-it.readme.io/docs/ldap-sync-login#field-mapping-for-syncing"><i class="fa fa-external-link"></i></a>',
'save_ldap_first' => 'You must save your LDAP settings before testing. Save your settings on this page and then reload to test LDAP login and/or sync.',
'ldap_server' => 'LDAP Server',
@@ -119,34 +217,34 @@ return [
'ldap_server_cert_help' => 'Select this checkbox if you are using a self signed SSL cert and would like to accept an invalid SSL certificate.',
'ldap_tls' => 'Use TLS',
'ldap_tls_help' => 'This should be checked only if you are running STARTTLS on your LDAP server. ',
- 'ldap_uname' => 'LDAP Bind Username',
- 'ldap_dept' => 'LDAP Department Field',
- 'ldap_phone' => 'LDAP Phone Number Field',
- 'ldap_jobtitle' => 'LDAP Job Title Field',
- 'ldap_country' => 'LDAP Country Field',
+ 'ldap_uname' => 'LDAP Bind DN/UPN',
+ 'ldap_dept' => 'Department Field',
+ 'ldap_phone' => 'Phone Number Field',
+ 'ldap_jobtitle' => 'Job Title Field',
+ 'ldap_country' => 'Country Field',
'ldap_pword' => 'LDAP Bind Password',
- 'ldap_basedn' => 'Base Bind DN',
+ 'ldap_basedn' => 'Search Base DN',
'ldap_filter' => 'LDAP Filter',
'ldap_pw_sync' => 'Cache LDAP Passwords',
'ldap_pw_sync_help' => 'Uncheck this box if you do not wish to keep LDAP passwords cached as local hashed passwords. Disabling this means that your users may not be able to login if your LDAP server is unreachable for some reason.',
- 'ldap_username_field' => 'LDAP Username Field',
- 'ldap_display_name' => 'LDAP Display Name Field',
+ 'ldap_username_field' => 'Username Field',
+ 'ldap_display_name' => 'Display Name Field',
'ldap_display_name_help' => 'If you have a separate displayName field in your LDAP/AD, map it here and it will be used for displaying users within Snipe-IT.',
- 'ldap_lname_field' => 'LDAP Last Name Field',
- 'ldap_fname_field' => 'LDAP First Name Field',
+ 'ldap_lname_field' => 'Last Name Field',
+ 'ldap_fname_field' => 'First Name Field',
'ldap_auth_filter_query' => 'LDAP Authentication query',
'ldap_version' => 'LDAP Version',
- 'ldap_active_flag' => 'LDAP Active Flag',
+ 'ldap_active_flag' => 'Active Flag',
'ldap_activated_flag_help' => 'This value is used to determine whether a synced user can login to Snipe-IT. <strong>It does not affect the ability to check items in or out to them</strong>, and should be the <strong>attribute name</strong> within your AD/LDAP, <strong>not the value</strong>. <br><br>If this field is set to a field name that does not exist in your AD/LDAP, or the value in the AD/LDAP field is set to <code>0</code> or <code>false</code>, <strong>user login will be disabled</strong>. If the value in the AD/LDAP field is set to <code>1</code> or <code>true</code> or <em>any other text</em> means the user can log in. When the field is blank in your AD, we respect the <code>userAccountControl</code> attribute, which usually allows non-suspended users to log in.',
- 'ldap_invert_active_flag' => 'LDAP Invert Active Flag',
+ 'ldap_invert_active_flag' => 'Invert Active Flag',
'ldap_invert_active_flag_help' => 'If enabled: when the value returned by LDAP Active Flag is <code>0</code> or <code>false</code> the user account will be active.',
- 'ldap_emp_num' => 'LDAP Employee Number Field',
- 'ldap_email' => 'LDAP Email Field',
- 'ldap_mobile' => 'LDAP Mobile Field',
- 'ldap_address' => 'LDAP Address Field',
- 'ldap_city' => 'LDAP City Field',
- 'ldap_state' => 'LDAP State/Province Field',
- 'ldap_zip' => 'LDAP Postal Code Field',
+ 'ldap_emp_num' => 'Employee Number Field',
+ 'ldap_email' => 'Email Field',
+ 'ldap_mobile' => 'Mobile Field',
+ 'ldap_address' => 'Address Field',
+ 'ldap_city' => 'City Field',
+ 'ldap_state' => 'State/Province Field',
+ 'ldap_zip' => 'Postal Code Field',
'ldap_test' => 'Test LDAP',
'ldap_test_sync' => 'Test LDAP Synchronization',
'license' => 'Software License',