Using the TXT record for SPF and DKIM is not easy

Descriptive title for this enhancement

The field to enter the txt record in the dns plugin is to short

Actual behavior

The field is way too short to manipulate txt record, we have to copy the record in a text editor to be able to manipulate it correctly.

Expected behavior

Be able to edit the record inside fusiondirectory without having to copy it elsewhere. It would be maybe better to have a the possibility to add a list of entries in the form of a https://fusiondirectory-developer-documentation.readthedocs.io/en/latest/pluginsystem/attributes.html#arrayattribute-and-setattribute

allowing us to add an entry for each line of the txt record, this would be particulary usefull in the case of spf record for example.

as a spf record look like this

v=spf1 mx a:gitlab.fusiondirectory.org a:admin.fusiondirectory.org -all

Step by step description of new behaviour

1. Create a new txt record
2. Add each entry of the record on his own line
3. save it

Benefits

• easier edition
• easier visualisation of whats inside when editing it
• less prone to typing errors

Possible Drawbacks

• need to reassemble the record to test the validity
• more difficult to maintain ?

Applicable Issues

spf records

created branch 5795-the-field-to-enter-the-txt-record-in-the-dns-plugin-is-to-short

mentioned in commit 278ae1f3

I changed for a text area which seems more natural and allows to edit on multiple line if needed. Please test and tell me what you think.

added 30m of time spent at 2018-03-15

added To Be Tested plugin-dns labels

Just tested on demo-dev and it look ok for me

closed

added 15m of time spent at 2018-03-15

added Changed and removed To Be Tested labels

changed the description

reopened

Added comment on how to make this work graphicaly

added 5m of time spent at 2018-03-15

changed the description

changed title from the field to enter the txt record in the dns plugin is to short to the field to enter the txt record in the dns plugin is too short

So, can you clarify what is expected here? We’ve established that storing newlines in the TXT field value is a bad idea as it may confuse tools reading the LDAP value.

What we could do is split the TXT into lines using a rule, like each 80 chars, or each 2 spaces.

Do you want something specific to SPF records or is the purpose for all TXT records? In the case of SPF records, isn’t the TXT record always a duplicate of the SPF one? Maybe in this case we could just put a checkbox in the SPF record edition to say we want to add it as both SPF and TXT with the same values and detect that when loading LDAP values?

added Need Info label

hello,

we can revert the change for 1.3.

we need to design a specialised way of making spf easy to use

Cheers

removed Need Info label