The problem....
We have a Web Application that bring in articles from various sources such as (google, bing, yandex).
We wish to add another source. The source is email subscriptions from scientific journals of which there are thousands.
We want our userbase to be able to signup for email subscriptions and pull them into the Web Application. As the subscription process requires an email and a confirmation of email step, this is pretty user unfriendly if an admin has to go and check emails all the time. We have a proposed workflow and would be interested to implement something like the following.
Proposed workflow
User goes to a custom subscription management page in our web
application
User enters the name of the subscription.
User presses 'save' User receives a unique email address from the application (i.e. subscription1233167845#mydomain.com)
user then takes this email and uses it to sign up for the email subscription with the scientific journal
system receives email from scientific journal asking for confirmation
system automatically verifies email address
email alerts received for journal
From here there are 2 possibilities
1) the application parses all resources in email and extracts links
which are submitted to the applications custom crawler
2) information
is scraped directly from email and added to the web application list
of articles
can it be done? Do you have a better way?? Thoughts?
Related
Honestly, I am not sure how to describe my specific problem but I can give a concrete example.
You have a web page that asks users to connect various social media accounts. Once they do this, you provide the connected accounts to a backend which can connect to each social media account (using oauth or auth or whatever) to pull different data and provide a social media analytics report. Assume this is all secure and safe, this is not the main concern.
Now suppose the following:
A third party website uses your services to determine if users can be eligible for sponsorship based on your analytics reports. They have their own form that they request users to fill out and at some point the form re-routes the user to your web page for the social media analytics part. Upon completion, your site must send that user back to the third party's website with the social media analytics report. How would you do this, securely?
I thought of something like the following:
The third party routes their user to your website by making a GET request with the following parameters: applicationId=some_third_party_application_id&callbackUrl=their_callback_url.
Your webpage could pull the applicationId and the callbackUrl from the parameters and cache it in localstorage or whatever.
The user goes through your flow by connecting various social media accounts and your webpage sends these connections to a server which computes the social media analytics report.
The analytics report id is returned to the webpage by your backend and now the webpage can send back this id of the analytics report to the callback url that was initially specified in step 1.
The flow resumes on the third party's webpage and they can then call another api of yours to get the analytics report details from the id of the report you sent back via the callback url.
The third party then uses the details of the report to determine if the applicant is worthy of sponsorship.
I guess another example of this flow could be like credit reports for like a car loan or something. You would apply for a loan on one website that integrates with a credit provider. The credit provider sends back the report to the auto loan provider and this is done seamlessly and securely.
How is this done/implemented in the examples I have outlined securely? Are my thoughts on the right track?
I integrated my application with the chatbase, but I would like my clients to have direct access to their email directly, as if it were a single step.
When I click a button in my application, it is directed to the logged-in chatbase screen.
Today I can only get it to the login screen, where it is still necessary to put the password to go to the dashboard, not logging directly into the application.
Is this possible? if yes, is there any kind of quickstart?
I followed the tutorial below to get to the login area, remembering that I use node.js
https://scotch.io/tutorials/easy-node-authentication-google
Thank you for your interest in Chatbase. There is currently no support for OAuth logins. Please see our recommended steps for third party integrations below:
Have the user open a Chatbase account with a Google linked email address
Have the user create a Bot in order to obtain the API key
Have the user integrate their analytics on your platform by providing the API key
Send the messages from their bot to their Chatbase API
Provide the user deeplinks to the Chatbase reports from within your UI
I have a web application wherein our users create contracts and we have integrated with DocuSign through an embedded recipient experience.
My web application is fairly involved in gathering the appropriate signers, sending emails, requesting signatures, keeping up with signer statuses, etc., and so I believe that an embedded recipient experience makes the most sense for us.
However, our first client using the integration has already been using DocuSign for some time and their signers (CEOs, CFOs and the like) are accustomed to logging into DocuSign, seeing envelopes in their inbox and clicking on them to sign - which is only possible in an integration by adding them as remote recipients. Embedded recipients cannot be associated to a DocuSign user account.
I'd like to keep using embedded recipients, but my client desperately wants to see envelopes created from my application in their DocuSign user account inbox and sign them from there without first having to log into my application.
Is there any clever way to deliver such a request with an embedded recipient experience? Even an atypical workaround, like sharing documents between the embedded recipient and the user account or some other recipient type of which I'm not aware, etc.?
Unfortunately not. When creating an embedded signing session the recipient becomes what's referred to as a Captive Recipient. Captive Recipients follow a different set of rules in regards to email notifications and presence in an inbox.
For example, Captive Recipients don't receive email notifications by default -- but they can supply an email to be CC'ed onto the envelope.
Since the Captive Recipient also has a universal account number, the user is technically part of an account outside of yours or your recipients.
IE: Your recipient views his inbox linked to his userId on account XXXXXXXXX.
The Captive Recipient is part of account YYYYYYYYYY with its own unique userId, so there's nothing for it to match up to.
If your app relies on embedded signing to load DocuSign envelopes into something like an iFrame, you can still do that without using an embedded recipient, which would give you the ability to load them through your webApp as well as let your signer access them via his DocuSign inbox.
To retrieve the signing URL, you make a POST call to https://{endpoint}.docusign.net/restapi/v2/accounts/{accountId}/envelopes/{envelopeId}/views/recipient with the following call body:
{
"returnUrl": "http://localhost/returnUrl",
"authenticationMethod":"email",
"email": "{recipientEmail}",
"userName": "{recipientFullName}",
"recipientId":"{recipientId}"
}
I have restricted the account creation to only bureaucrats. That is, only bureaucrats can create accounts for other users.
A confirmation email is sent to the newly created user on successful account creation in MediaWiki. But, would like to know where can i change the content of Confirmation Email template that i receive in MediaWiki.
Where can i find the various email templates used in MediaWiki?
For eg: Content of Confirmation Email upon successful account creation is as below.
Someone, probably you, from IP address ::1,has changed the email
address of the account "Admin" to this address on admin's Wiki!.
To confirm that this account really does belong to you and reactivate
email features on admin's Wiki!, open this link in your browser:
I would like to change the above content but couldn't find where these email contents are stored or from where it is invoked.
Any help is appreciated.
The email templates are stored as normal system messages, in the MediaWiki namespace, e.g. MediaWiki:Notificationemail_body_changed.
You can filter out all relevant system messages like this: Special:AllMessages&prefix=Notificationemail
Currently, there are four:
MediaWiki:notificationemail_body_changed
MediaWiki:notificationemail_body_removed
MediaWiki:notificationemail_subject_changed
MediaWiki:notificationemail_subject_removed
Those pages will give you the message in your wiki's default language. To change a specific language (that a user might have chosen), use MediaWiki:notificationemail_subject_removed/ar (Arabic), MediaWiki:notificationemail_subject_removed/en (English), etc
#leo's answer is correct for messages sent regarding email authentication.
All other email messages as related to changes in pages, etc., are stored in system messages that start with enotif_, and you can see them all using this filter:
Special:AllMessages&prefix=enotif_.
The messages for vanilla* MediaWiki are:
enotif_impersonal_salutation
enotif_subject_deleted
enotif_subject_created
enotif_subject_moved
enotif_subject_restored
enotif_subject_changed
enotif_body_intro_deleted
enotif_body_intro_created
enotif_body_intro_moved
enotif_body_intro_restored
enotif_body_intro_changed
enotif_lastvisited
enotif_lastdiff
enotif_anon_editor
enotif_body
And you can see them all using this filter:
Special:AllMessages&prefix=enotif_
* People using extension:Echo have a few other messages to change.
My web site has an opt-in form for user's email addresses. The form will have fields such as name, email and phone number.
Upon submission, I would like the data to also be inserted into my MySQL database.
However, I would also like the email address to be added to an AWeber email subscriber list.
Is this possible?
Yes, it is posible to store the data in a database.
Posting data via a 3rd party script is against Awebers Terms of Service. So it is necessary to take another route.
The way to do it is to allow your user to submit their information to Aweber via the JavaScript form, but choose the setting to request that Aweber send the user information back to you, via your thank you page.
You can use the thank you page to store the user data in your database.