As of now I cannot seem to get my Alexa skill linked with twitter. Currently, I have a node/express server running on EBS which, I am using passport-twitter to handle the oauth part of the authentication. Right now my flow is such:
Enable skill in Alexa app
Click 'sign in to account' in alexa app
Twitter Login screen is displayed and I enter user name and password then click Login button
get redirected to Amazon provided url for callback once authenticated and get an 'Unable to link you skill'.
I login and everything, so I think issue is with redirection, which is defined in the twitter auth callback on my express server like so:
app.get('/auth/twitter/callback',
passport.authenticate('twitter', {failureRedirect: '/login'}),
function(req, res){
var redirectUrl= 'https://pitangui.amazon.com/spa/skill/account-linking-status.html?vendorId=M28J2SR508CPU9#state='
+state+'&access_token='+myToken+'&token_type=Bearer';
res.redirect(302, redirectUrl);
});
My redirect url, minus the sensitive data, is
https://pitangui.amazon.com/spa/skill/account-linking-status.html?vendorId=M28J2SR5BLAH#state=&access_token=&token_type=Bearer
Any ideas on how to debug/troubleshoot as well as any suggestions to fix issue would be awesomely appreciated.
You have a hash ('#') before the 'state' URL parameter. Perhaps you meant for that to be an ampersand ('&')?
https://pitangui.amazon.com/spa/skill/account-linking-status.html?vendorId=M28J2SR5BLAH&state=&access_token=&token_type=Bearer
Related
I have an app that all works fine for authentication and it uses Oauth2 (Google).
Now, I am struggling with the logout URL for this app. It works, but I am under the impression that it is possible to logout of it and remain logged into my gmail account please? Currently, ALL accounts are logged out of so the two gmail accounts need to go through login each time the app is used and log out is pressed.
I have read that this is possible but this is the URL that I am using to Log out
https://www.google.com/accounts/Logout?continue=https://appengine.google.com/_ah/logout?continue=http://news.bbc.co.uk
I am sure it can be done because I did it in a former role but do not have the code!
We have an iOS app connected to Firebase that calls on the Twitter API for authentication. We are being redirected fine to the Twitter form to enter crendetials. After entering the account and password, our callback_url is not executed and instead we see “Nothing to see here”. Does anyone else is having this issue?. The Twitter Developer Portal is configured fine with Firebase's callback URL, also have the website, terms and policy fields set. I guess if anything wrong at the portal we wouldn't be redirected from the app to the sign-in form. Any ideas?
I logged with my twitter # username and it worked. However the problem persists if logging using email address.
I'm trying to connect to Freshdesk using OAuth 2.0, for single sign-on from my app. My app is serving as it's own OAuth identity provider. I've set up my Authorization url on Freshdesk -- let's call it https://www.myWebApp.com/auth:
So now for testing purposes I go to the URL that Freshdesk support provided for a user to initiate the single sign-on process:
https://myWebApp.freshdesk.com/login/normal
...and I see a nice sso-style login screen:
I enter a correct email and password for one of my site users and click "Login".
Now in the Chrome network tab, I would expect to see Freshdesk trying to ping my Authorization URL. But I don't. I see this:
When loaded, my auth page (https://myWebApp.com/auth) pings my server, which issues a console.log() message, and my server logs show no such console log message -- so Freshdesk doesn't seem to be pinging my auth page at all.
What is keeping Freshdesk from pinging my auth page as it should?
There is probably a fair bit here that you have in place already but I am just adding it in for completeness.
Logged into the backend and on the security page for contacts
https://stackoverflow.myfreshworks.com/security/contacts
[stackoverflow == your site :) ]
you will have to create a Custom Policy if you don't have one in place already (this is different to the one for Agents)
And for that configure your SSO with Oauth 2.0
Then , if you have at least one SSO configured your login (at https://stackoverflow.freshdesk.com/support/login ) should look like this:
Where (1) now appears. That will be the link to ping your server via the urls you set up for the SSO:
If you only have one SSO set up for your contacts that link (1) should complete the sign-in process directly and then you should end up logged into Freshdesk as the specific contact.
If you had two SSO options set up; for example:
..when you clicked the link (1) on the https://stackoverflow.freshdesk.com/support/login page, you should then be redirected to a page with those two options:
The url for that page is something like (parameters will be different for you):
https://stackoverflow.myfreshworks.com/login
?redirect_uri=https://stackoverflow.freshdesk.com/freshid/customer_authorize_callback
&client_id=14416083630394368&slug=6117145232763
I am imagining you could use that as a direct link to the portal on your main site.
If you only have one SSO option set up you should be able to navigate directly to the link as above and then see :
which is probably what you are aiming for.
I changed the name of that button (Sign in with contacts SSO) just to be sure I was using the right one and to differentiate from the login for agents. You can change the text under the Advanced Options when configuring the SSO:
Hope this helps you along the way - if you have any other questions on this post them as comments.
We are creating alexa skill and trying to do account linking. We have setup the below steps so far for account linking :
Setup Authorization URI API
https://[abcapp].herokuapp.com/userdetails/accountlinking
For Authorization API we are redirecting on AWS account login URL. Please see below URL
https://www.amazon.com/ap/oa?client_id={0}&scope=profile&response_type=code&state={1}&redirect_uri={2}
Here redirect_uri is our custom signup URL
https://[abcapp].herokuapp.com/userdetails/signup
In signup page we are calling web request for url https://api.amazon.com/auth/o2/token to get access_token and refresh_token
In signup page we ask user to input details and save these details in our database for future interaction with alexa skill to manage user details in database
After successfully authentication, we are redirecting on following URL :
https://pitangui.amazon.com/spa/skill/account-linking-status.html?vendorId=[VenderID]&token_type=Bearer&access_token={0}&state={1}&code={2}
When we are trying to connect alexa skill, I am successfully able to login with AWS , after that I am able to enter user details on signup page. Now we are redirecting user to alexa linking status page but we are getting error as "We were unable to link at this time"
Please see attached screenshot:
Can anyone help on this ?
I'm developing a desktop application which is supposed to allow users to login via Twitter.
There seems to be 2 ways to do so, that differ in a way oauth_verifier is returned to the application.
The first one is for web applications and oauth_verifier is returned as a url query parameter when redirecting user back to redirect_url.
The second one is using a PIN displayed to the user, which user enters to the app.
Now Facebook, for example, has a page facebook.com/connect/login_success.html , where FB can redirect a user with ouath_verifier as a query param (e.g. facebook.com/connect/login_success.html?code=<token>. Then I can read that param back from the browser's location field (I'm using an embedded browser).
So, is such a workflow possible with Twitter? Does it have a static page, where it can redirect user with oauth_verifier ?
I haven't been able to find such a page in Twitter's API docs, so I ended up using the main page twitter.com for the redirect. Everything works fine.