With EJBCA CE v9.3.7, Wildfly 35, PostgreSQL 16, Java 21, on Rocky 9. Firefox 152.
Tests made with a superadmin account on the adminweb
To extend #904, I tested with a new cryptotoken, a new (root) CA, default ENDUSER certificate profile and a minimal EE profile.
In the EE profile, I set "Send notification":
- Use
- Default
- Enforce default
- Add
- sender = user = root@localhost
- subject = foo
- text = bar
I create an EE without any issue and retrieve its P12 certificate.
I then search the EE, edit it, set it to new, and define password, (**Send Notification is activated and grayed"). I get an exception "An exception has occurred". Message in log is "Userdata did not fulfill end entity profile 459019223, dn 'CN=test1609': Email notification is required.."
If I remove "Default" for notification ("Enforce default" in set):
- adminweb let me activate or not "Sent Notification" => seems wrong
- If I activate "Send Notification" when I edit the EE, same error => OK with profile
- If I do not activate, the edition succeed => OK with profile
If I unset "Enforce default" for notification in the profile, saving new status for the EE succeed, whether I activate "Send Notification" or not.
Now with the "new" RA:
- Search EE
- Edit it
- Set status to "new" and enrollment code
- And it succeed!
The issue is probably bound to the adminweb.
With EJBCA CE v9.3.7, Wildfly 35, PostgreSQL 16, Java 21, on Rocky 9. Firefox 152.
Tests made with a superadmin account on the adminweb
To extend #904, I tested with a new cryptotoken, a new (root) CA, default ENDUSER certificate profile and a minimal EE profile.
In the EE profile, I set "Send notification":
I create an EE without any issue and retrieve its P12 certificate.
I then search the EE, edit it, set it to new, and define password, (**Send Notification is activated and grayed"). I get an exception "An exception has occurred". Message in log is "Userdata did not fulfill end entity profile 459019223, dn 'CN=test1609': Email notification is required.."
If I remove "Default" for notification ("Enforce default" in set):
If I unset "Enforce default" for notification in the profile, saving new status for the EE succeed, whether I activate "Send Notification" or not.
Now with the "new" RA:
The issue is probably bound to the adminweb.