Full domain name as user and group

Submitted by rrdoo on Mon, 10/01/2018 - 07:08

Hello.

-Centos 7 (latest update) - did not check on other OS-es

-Virtualmin (latest update) with LDAP backend

If we use full domain name (domain.com) for user and group name, we get the following error:

Creating administration group domain.com ..
Use of uninitialized value $_[3] in concatenation (.) or string at /usr/share/perl5/vendor_perl/Convert/ASN1/_encode.pm line 152.
Adding webserver user apache to server's group ..
Use of uninitialized value $_[3] in concatenation (.) or string at /usr/share/perl5/vendor_perl/Convert/ASN1/_encode.pm line 152.
.. done

Everything seems to work OK, virtual servers are working normally, user can login, but I would still like to ask if this is a problem and if it's a bug that needs to be fixed.

Thank you very much!

Status: 
Active

Comments

Submitted by andreychek on Mon, 10/01/2018 - 10:10

Howdy -- thanks for your bug report!

Just to verify --

It sounds like you're saying that you are using LDAP... and if you use the default user format of user.domain, things work as expected. But if you change it to user@domain.tld, you're running into the above issues with that?

Submitted by rrdoo on Mon, 10/01/2018 - 10:39

I am sorry, I have the whole situation in my head and I did not clarify it enough. So here is more detailed explanation: We use the following setting in virtualmin:

System settings - Virtualmin configuration - Defaults for new domains - Domain name style in username --> Full domain name

We want to use full domain name as it's more convenient and more logical for our situation.

We use LDAP backend (I didn't check if this error is present with normal user storage)

We only use Apache hosting and MySQL (which turns dot(.) to underscore(_) for database name - which is great), but no mail, no dns.

So when we create a new virtual server the above error is present. But everything seems to work OK. So is this just a bug that doesn't effect anything? Or is something else wrong in the background (like something is configured wrong because of this settings, but it's not visible with normal use)?

Thank you!

Submitted by JamieCameron on Sun, 10/07/2018 - 17:47

That error is coming from somewhere deep inside the Perl LDAP module, so it's hard to debug what Virtualmin is going wrong that is making the module unhappy. However, if users and groups work fine, I'd recommend just ignoring it.