OPNsense
  • Home
  • Help
  • Search
  • Login
  • Register

  • OPNsense Forum »
  • Profile of nantoine555 »
  • Show Posts »
  • Messages
  • Profile Info
    • Summary
    • Show Stats
    • Show Posts...
      • Messages
      • Topics
      • Attachments

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

  • Messages
  • Topics
  • Attachments

Messages - nantoine555

Pages: [1]
1
18.1 Legacy Series / Re: Edit LDAP Users: "The username contains invalid characters" when using an AD UPN
« on: March 06, 2018, 07:30:50 pm »
I'll just have to explain to my users that they'll have to enter their windows account and not their email when login to the vpn ;D

2
18.1 Legacy Series / Re: Edit LDAP Users: "The username contains invalid characters" when using an AD UPN
« on: March 05, 2018, 02:32:54 pm »
Ok, opening an issue on github, found the following code:

        if (preg_match("/[^a-zA-Z0-9\.\-_]/", $pconfig['usernamefld'])) {
            $input_errors[] = gettext("The username contains invalid characters.");
        }
        if (strlen($pconfig['usernamefld']) > 32) {
            $input_errors[] = gettext("The username is longer than 32 characters.");
        }

3
18.1 Legacy Series / Edit LDAP Users: "The username contains invalid characters" when using an AD UPN
« on: March 05, 2018, 11:55:19 am »
Hello,

We are importing users from an Active Directory.

In the LDAP configuration, the User naming attribute is userPrincipalName, so the Usernames are in UPN form (user@domain.com).

First import from LDAP is fine, but we are unable to edit and save users:
"The username contains invalid characters"

I think it is only a html form validation issue, but are any other issues when a username contains "@" and "." characters?

Thanks, and keep doing such a fine job :)

Antoine

Pages: [1]
OPNsense is an OSS project © Deciso B.V. 2015 - 2023 All rights reserved
  • SMF 2.0.19 | SMF © 2021, Simple Machines
    Privacy Policy
    | XHTML | RSS | WAP2