I'm new to Node-red and Bluemix
I'm trying to get a Twitter feed
I added the Twitter input node to the workspace.
I can't get the "add new twitter credentials" working :(
I click on the pen next to the select box, and new screen opens to auth that I use the twitter credentials (logged in as a Twitter user in another tab in EDGE browser). I accept and get the success message and that I can close the window.
However, nothing happens in the Node-red editor. If I deploy, I get an error message in the debug window: Missing twitter credentials
What am I doing wrong?
Thanks
Nico
Thanks,
the problem was Microsoft Edge.
Chrome in Android works like a charm for Node-red on Bluemix :)
Related
I am using Trino to connect to PrestoSQL for my organization in the manner below with python. The MFA authentication requires that I click a link to authenticate. The links usually look something like this: https://query.organization.com:6543/oauth2/token/initiate/b74d83f9e395e4c27d18b
Once I click the link, a JuypterLab window (screenshot below) opens, which requires me to enter my username and password. After I do that, it just keeps spinning eternally and never ends up connecting or going through. (I am using Trino jar jdbc-367, if it matters.)
This only happens in the desktop app version of JupyterLab. This does not happen in the web version of JupyterLab, nor does it happen in JupyterNotebook. On the web versions, when I click the link and enter my username/password, it allows me to connect and to proceed with my query. Is there any reason why JupyterLab desktop version cannot go through?
connect = trino.dbapi.connect(
host='query.org.com',
port=6543,
user='hsimpson',
catalog='cloud9',
http_scheme='https',
auth=trino.auth.OAuth2Authentication()
)
https://i.stack.imgur.com/29t8A.png
Introduction
I've been trying to build a Google Home, Smart Home Activity that integrates with Azure AD. I've been able to correctly sign in so the ClientId/endpoints/scopes must be correct.
When I try to connect to the Smart Home skill using the simulator it shows me an error that this functionality isn't supported in the simulator. So I then moved to my actual android phone. However when I try to link to the smart home service in the google home app it correctly asks me to login, but after logging in the login screen disappears and I'm back to selecting a service I want to link to.
Flow to activate service:
So after the 4th image it just goes back to the original screen and no skill was ever added.
I've also setup NGROK as my fullfillment URL but I see no activity other then some of my own tests:
My configuration
This is the way I've set everything up:
Azure AD:
I've also configured the direct URL to be: https://oauth-redirect.googleusercontent.com/r/davysmarthome
Google Home (Action):
Google Home (OAuth):
Summary
My question would be why my skill doesn't want to be linked to. I have not yet implemented anything in my actual API yet but I would expect NGROK to at least show some data traffic if google home would actually try to link itself and request what devices are connected.
After analyzing the 4th image, it can be seen that you haven't enabled "Testing" on your project, sometimes the Account Linking process fails if testing has been disabled for any reason. To make sure testing is enabled for the project, go to AoG Console > Develop > Account Linking > Test (Upper Right Corner).
But, in this case, it does not necessarily mean that the account linking failed, it is also possible that account linking succeeded, but failed in SmartHome Sync. To make sure if account linking has succeeded, please visit https://myaccount.google.com/accountlinking?hl=en and check if the account has been linked correctly.
There are other tools available that can help you with debugging OAuth issues such as "OAuth Playground". It helps in finding out the exact issue causing the error.
I have been trying to implement the OAuth v2 for Microsoft Accounts for my website. Its currently in development stage and so am testing on localhost. The Website is an ASP.NET Core MVC 5 Application.
I have followed the tutorial here to implement OAuth for Twitter, Google and Facebook accounts. I found this to be quite simple with only a few small issues that I was able to solve with simple google searches.
However I have spent several days trying to understand what is happening when trying to use Microsoft Account authentication on my site.
I have watched the video here on registering an application in the Microsoft App Registration Portal. At around minute 6 in the video a short demo shows how to set up the App. You can see my App details in the following screen shot:
In the video at about 7.5 mins in, there is a small section explaining how to test the App by building a URL string.
On submitting the query string to the browser the page is redirected as expected to my App page as you can see here:
In this instance I was all ready signed into my Microsoft Outlook account. If I wasn't signed in I would be prompted to login to a Microsoft account. Logging in, in this case choosing my already signed in Outlook account causes the page to be redirected back to my site as seen in the following screen shot but because the site didn't send the request its not expecting a token sent back for login so nothing really happens. This is expected behaviour, at this point as I was only testing that the Apps end point was working as expected.
[
The next stage is to test the functionality from my website. This is where I always have issues. To activate the OAuth functionality for Microsoft Account login requires simply un-commenting a couple of lines of code within the Startup.Auth.cs file in my websites App_Start folder and passing in the Apps ClientKey and ClientSecret values as can bee seen in the following code snippet:
app.UseMicrosoftAccountAuthentication(
clientId: System.Configuration.ConfigurationManager.AppSettings["MicrosoftOAuthClientID"],
clientSecret: System.Configuration.ConfigurationManager.AppSettings["MicrosoftOAuthClientSecret"]);
This code basically adds a little button to the login page that allows you to choose Microsoft login as can be seen here:
[
When I click the Microsoft button I get the following error page:
And the query string returned contains the following:
https://login.live.com/err.srf?lc=2057#error=unauthorized_client&error_description=The+client+does+not+exist.+If+you+are+the+application+developer%2c+configure+a+new+application+through+the+application+management+site+at+https://apps.dev.microsoft.com/.&state=JMxMRuKaOiYWCQw_Uqkhv3gLQn3ULlkG2miM4ymcHhTK5niXVQl5n4L0a6VoWeEKmFM7T1ciU2oQAh26_Y0i2DMjdt6BOAtpjNeMaSpBq4wbCjva9lOuctOUIWwoFdTEGvxJ4M904lUsoudd9e9cYi6eiH3JF81HB5ouQSus2ddE1sVUQLw-YB1GjUL79y2muFaBFIOIOk75oCV2IxX4cFO2rJU04K9Se6gxu698WpzR8taUB2c6tK9u0dBisckhavf0IvKB9dWQq-IVwQgvaA
Anybody know why or what is happening????
Now I have read in several of my many searches while trying to understand whats happening when I try to test the App from my site rather than a URL directly in the browser that I should have
/signin-microsoft
appended to my Redirect URL in the App Portals configuration. I have Tested with my Redirect URL set like that and this does not work. I get a HTTP ERROR 500 sent back because the page signin-microsoft does not exist. So this is not my problem.
Please help if anyone has had the same issues and solved it.
EDIT: I should have mentioned that I was initially trying this using Local IISExpress but after reading some posts saying it can be done only on IIS so I published my site locally to IIS.
To Authenticate the app , simple way is I get a ticket by this method "GET https://www.box.com/api/1.0/rest?action=get_ticket&api_key=" and finally " https://m.box.com/api/1.0/auth/ " the url open up the login page in safari, it was easy in v1 iOS SDK.Now I could not able to authenticate after entering credentials and clicking login I cannot enter into my application. I have been facing authentication issue. How to authenticate using new iOS SDK v2 ?
What error u getting?
Also Try using POSTMAN Google chrome extension to do the authentication as a command line and try to implement on your real app, u will find supportive docs on Box website. Make sure all your parameters are correctly entered.
When logging in via Google (through Asana Connect from iOS App) the following error gets presented in the browser window: 'invalid_request: The required parameter 'redirect_uri' is missing.'
Logging in via username and password works absolutely fine.
Is that an issue at my end or within the Asana Connect API ?
Any idea how to fix this issue ?
A very interesting thing though ... when going back to the app and logging in again, the authentication happens successfully without asking for user credentials, returning to the app with valid accessToken & refreshToken.
I too use GTMOAuth for mac. This error occurs because in a normal web browser when we click login with google account, a new browser window opens to get credentials. using GTMOAuth it embeds only a single webview and so its unable to present a new browser window for google credentials to be used.