Description of problem:
'Cockpit had an unexpected internal error.' when creating a new sasl mapping


Version-Release number of selected component (if applicable):
cockpit-389-ds-1.4.2.9-1.module+el8dsrv+6001+1cbc6dcf.noarch

How reproducible:
always

Steps to Reproduce:
1. Go to 'SASL settings and mappings'
2. Click 'Create new mapping'
3. Enter value for each field
4. Click 'create mapping'

Actual results:
message 'Ooops!' at the top right of the console
New mapping appears in the Sasl mappings table

Expected results:
cockpit does not crash

Additional info:

Javascript console details :
CMD: loadConfig: Get SASL settings ==> dsconf -j inst1 config get
index.js:sourcemap:83 CMD: loadMechs: Get supported SASL mechanisms ==> dsconf -j inst1 sasl get-mechs
index.js:sourcemap:83 CMD: get_and_set_sasl: Get SASL mappings ==> dsconf -j inst1 sasl list --details
index.js:sourcemap:83 CMD: createMapping: Create sasl mapping ==> dsconf -j inst1 sasl create --cn=example_map --nsSaslMapFilterTemplate=cn=\1 --nsSaslMapRegexString=\(.*\) --nsSaslMapBaseDNTemplate=ou=people,dc=example,dc=com --nsSaslMapPriority=100
index.js:sourcemap:83 CMD: loadConfig: Get SASL settings ==> dsconf -j inst1 config get
index.js:sourcemap:83 Uncaught TypeError: e.props.addNotification is not a function
    at Function.<anonymous> (index.js:sourcemap:83)
    at s (cockpit.js:sourcemap:979)
    at cockpit.js:sourcemap:991
    at n (cockpit.js:sourcemap:897)
index.js:sourcemap:83 CMD: loadMechs: Get supported SASL mechanisms ==> dsconf -j inst1 sasl get-mechs
index.js:sourcemap:83 CMD: get_and_set_sasl: Get SASL mappings ==> dsconf -j inst1 sasl list --details
index.js:sourcemap:83 CMD: loadConfig: Get SASL settings ==> dsconf -j inst1 config get