LFDS new user email validation on form

replied on October 10, 2019

Chase -

Thanks! In the meantime, what should I do to bypass the issue to allow me to create the user within the system? Ie. how do I create a user at this point whose address I cannot enter in LFDS? I need to create this account, but the system will not allow me to do so - what is the workaround?

To add to any ticket that may be open regarding validation rules:

You should not rely on any lookup list to determine what is a valid TLD. The only way to validate an address would be to:

Validate the format, ie. check the 'local part' to have letters, digits or the characters !#$%&'*+-/=~_`{}| or . The address may be quoted to include a sequence of . characters, for instance, and may also be an internationalized format using characters encoded in UTF-8... Then, check the 'domain part' to comply to hostname requirements, which would include characters and digits, and the hyphen. Internationalization rules come into play there too... Also, validate that the local and domain parts are separated by the @ symbol...
The local part may be no longer than 64 actual characters (UTF-8 can play havoc with a simple count)
Validate that the domain has an MX record in DNS, or if no MX record, that at least an A or AAAA record exists for the domain.

Of especial note is to consider that the following *IS* a valid (except for the use of the reserved domain example.com):

" "@example.com

This is another valid address:
संपर्क@डाटामेल.भारत

I've read of other situations here on answers where a question has come up with the validation rules for email addresses, and it is disheartening to see that broken validation rules have been implemented on a platform of this caliber...

1 0

SELECTED ANSWER

replied on October 10, 2019

A workaround you can try is this:

Create the user with all claims except email
Execute the following SQL query after backing up your database (replacing <email> and <userSid> with the desired email value and the desired user's SID):

update additional_claims
set str_val = '<email>'
where sid = <userSid> and claim_id = 1

Note: any time you want to update the user's claims you will need to remove the email value to save changes and then you must re-run the query to re-add their email.

0 0

replied on October 10, 2019

OK - that works, though I really did not want to have to modify things directly in the DB on a per-user basis. Would much rather have been able to modify the validation rules, or disable validation entirely on the back-end process for LFDS. It is nice to see some validation there, but since it is an administrative tool, the assumption would be that the user entering data would have a clue...

0 0

replied on March 11 • Show version history

Updated workaround:

1) Open C:\Program Files\Laserfiche\Directory Server\Web\LFDS\Release\Scripts\app.min.js

Important: this will need to be re-updated after any upgrades/updates installed for LFDS

It will look something like this:

provider('EmailTestService', function ()
{
	var self = this;
	var filter = /[a-z0-9!#$%&'*+/=?^_`{|}~-]+(?:\.[a-z0-9!#$%&'*+/=?^_`{|}~-]+)*@(?:[a-z0-9](?:[a-z0-9-]*[a-z0-9])?\.)+(?:[A-Z]{2}|aero|arpa|asia|biz|cat|com|coop|edu|group|gov|healthcare|int|info|jobs|law|local|mil|mtn|mobi|museum|name|net|org|pro|tel|travel|xxx|xyz|wtf)\b$/i;

We will be adding this workaround to our documentation and have a backlog item to improve the overall handling.

0 0

replied on July 20, 2020

Is there any traction to this? Had to google the result when I was faced with another user with a similar issue - and came to this question again...

This should not be an impossible fix to implement - likely a simple patch to the lookup rules at the very least...

replied on July 21, 2020

Hi Kris,

This item is still in our backlog and I've updated it to note that another customer has run into the issue.

Question

Question

LFDS new user email validation on form

Answer

Replies

Sign in to reply to this post.