I have created 1 Web demo DialogFlow agent and i added the Iframe in my site. Now my requirement is that when logged-in user see this Agent window, automatically logged-in user's name should display - "Hi Monty".
I want to pass username and password silently to dialog flow from my website and then i will authenticate it with the help of Webhook and will fetch the profile and then will display the user's name in Agent.
Please let me know, how can i do this?
Related
I have embedded an iframe in the source code of each person added to my People plugin
I am looking for a way to conditionally render a button based on who the logged-in user is. If the email of the logged-in user matches the email in the iframe's param then the button ('Click here to update Profile') should appear. Otherwise, it is not on the page when the logged-in user views other people.
Buildfire People Plugin
I looked through the public api docs and tried using the /auth/verify_credentials but this is for logging in, this will not return the email of the logged-in user.
I know buildfire SDK has a buildfire.auth.getCurrentUser(callback) function that can be used. I need the callback to send that info to another application.
The app that I created is deployed on netlify and the backend is deployed on heroku.
I am new to build chat-bots. Here I have made a chat-bot using dialog flow and integrated with google assistant. Is their any way that we can get the mail id of the user interacting with the chat-bot so that we can send mail to their respective id.
Only with the user's permission to give it to you. You can request that they sign in using Google Sign In for Assistant. When they do so, their profile information is available. If their email address is part of their profile, it will be included.
I have AWS Cognito account linking setup with Actions on Google. I have requested the scope of email. I am using API.AI, how can I get the user's email? From what I've read, you get a userId that is basically an anonymous id. How can I get user details?
For getting user details like mail id etc, you would have to enable Account linking on your google home dialog flow console.
You would also have to provide an Oauth2 server to get the authorization done.
Refer to this : https://developers.google.com/actions/identity/account-linking
Once this is done, you will receive an auth_token every time your api.ai app is invoked. You will then have to use this token and retrieve the user details like mail id from Google API services.
Let me know if I need to add more details, in case its not clear.
Our application offers Docusign integration.
Therefore, we allow our users to Login to Docusign.
Everything is fine when the user is already a Docusign user and logs in:
User taps on Login to Docusign
A browser is opened and redirected to Docusign login dialog where he enters his email address
He enters the email address
He enters his password
He is redirected to callback_url
However, when the user needs to register to Docusign, the process becomes like this:
User taps on Login to Docusign
A browser is opened and redirected to Docusign login dialog where he enters his email address
Since he doesnt have an email registered with docusign, he taps on "Register" link
An activation email is sent to his email address.
user clicks on the activation link in the email
User is redirected to his Docusign dashboard
The problem with this registration flow is that on step 6, the user is not being redirected to callback_url.
Therefore, the loop with our application is now broken and user is confused.
Shouldn't Docusign redirect users back to callback_url when activation is completed?
If your application's User Experience (UX) explicitly enables the user to either create an account on DocuSign or to sign in, then you can remove the "Create an account" option from the OAuth window:
In your initial GET to the DocuSign authentication server, include query parameter of
ui_flavors=no_sign_up
This should prevent the "Sign Up" links / options from being shown.
This is not the optimal answer for the question, but it is available now.
We have an application that we currently open the DocuSign console in an IFrame. The issue is that currently we are having to open a new tab, log on to DocuSign and then the user can see the console in the Iframe with documents. What is the most common way people are using to automatically logon to DocuSign through their applications ? I see an SSO documentation but it says that it looks at the persons email domain to authenticate them.... our users will have many different email domains.
Your application can use the API to get the console view for the user. The session will correspond to the user credentials in your API request and will skip the logon step. From that API call you get a URL back that you can embed in the iFrame. E.g.: POST to https://demo.docusign.net/restapi/v2/accounts/55555/views/console and you get back a URL like this:
{
"url": "https://demo.docusign.net/Member/StartInSession.aspx?StartConsole=1&t=00000000-0000-0000-0000-000000000000&accountid=00000000-0000-0000-0000-000000000000"
}
Edit: If you need the "sending view" (sometimes called "the tagger") for an envelope then you can POST using a URL like this:
https://{server}/restapi/{apiVersion}/accounts/{accountId}/envelopes/{envelopeId}/views/sender
e.g.
https://demo.docusign.net/restapi/v2/accounts/12345/envelopes/f6e755d3-bbcf-44e5-b276-8ae626f97220/views/sender