Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 4.0.BETA
-
Fix Version/s: 4.0
-
Component/s: Push Library
-
Labels:None
-
Environment:Cloud Push
Description
Cloud Push supports a number of endpoints as delivery options - native (iOS, Android), SMS, etc. While these are all EE NotificationProvider implementations, the list also includes email - the only option we provide in the open source version of ICEfaces.
The task is to verify and, if necessary, fix the org.icepush.EmailNotificationProvider that we ship with ICEfaces.
The task is to verify and, if necessary, fix the org.icepush.EmailNotificationProvider that we ship with ICEfaces.
Activity
Deryk Sinotte
created issue -
Deryk Sinotte
made changes -
Field | Original Value | New Value |
---|---|---|
Assignee | Jack Van Ooststroom [ jack.van.ooststroom ] | |
Fix Version/s | 4.0 [ 11383 ] |
Ken Fyten
made changes -
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Ken Fyten
made changes -
Status | Resolved [ 5 ] | Closed [ 6 ] |
In order to verify this I used ICEpush Trunk in combination with NaaS due to its ease of the REST API.
I used a dummy Gmail account without success and my ICEsoft account with success.
Though I got this to work with my ICEsoft account, I feel that the EmailNotificationProvider could use some attention to figure out why it didn't work with the Gmail account, test it with a non-ICEsoft and non-Gmail account, test it with SSL and NONE security options, and maybe provide a test (in our bundle) that utilizes the JavaScript Bridge in order to set the User's e-mail address from within the Browser for instance.