11087
Reporter: lfrancke
Assignee: lfrancke
Type: SubTask
Summary: Save E-Mail address somewhere retrievable
Description: Once we have an E-Mail address to send a notification to we need to store that information somewhere so that the callback from Oozie can retrieve it.
Priority: Major
Resolution: Fixed
Status: Closed
Created: 2012-05-14 15:12:06.168
Updated: 2013-12-17 15:17:25.74
Resolved: 2012-05-18 17:26:18.576
Author: trobertson@gbif.org
Created: 2012-05-14 15:17:44.892
Updated: 2012-05-14 15:17:44.892
Do you want to pass in the email, or use user credentials?
I guess you need to pass it in, as I may be the logged in user, but I am running the download for someone else, so will put their email.
Author: lfrancke@gbif.org
Created: 2012-05-14 15:20:35.27
Updated: 2012-05-14 15:20:35.27
I don't understand the question.
I'd have thought that our JSON stuff takes a field "notification_address" and that can be a E-Mail address (or later if required a HTTP callback) where we send a message to.
The problem is that we don't save any of the job data anywhere but we need to access the e-mail address when the job's finished so I'm looking into saving it in the oozie job.
Author: mdoering@gbif.org
Comment: Do we only allow authenticated download? In that case downloading on behalf of someone else sounds like a misuse
Created: 2012-05-14 15:51:21.737
Updated: 2012-05-14 15:51:21.737
Author: lfrancke@gbif.org
Created: 2012-05-14 16:07:09.026
Updated: 2012-05-14 16:07:09.026
Ah, now I understand Tim's question, thanks Markus.
Well... I don't know. That's a decision for Tim I guess.
Depending on that decision I'll need help with authentication stuff etc.
Author: lfrancke@gbif.org
Comment: Can we continue this discussion in OCC-18 please?
Created: 2012-05-14 16:07:35.864
Updated: 2012-05-14 16:07:35.864