google-authentication

问题 I try to login with Google by using PassportJS. But when I use the custom callback, the Google Strategy never called the callback. What am I doing wrong? My codes are below. endpoints: var router = express.Router(); router.get('/', passport.authenticate('google', { scope: [ 'https://www.googleapis.com/auth/plus.login', 'https://www.googleapis.com/auth/plus.profiles.read', 'https://www.googleapis.com/auth/userinfo.email' ] } )); router.get('/callback', function (req, res) { console.log("GOOGLE

问题 I am working with google authentication in .net core but when redirecting from google it showing me exception- InvalidOperationException: No authentication handler is configured to handle the scheme: Cookies Here is my Setting for startup.cs app.UseCookieAuthentication(new CookieAuthenticationOptions { LoginPath = new PathString("/account/login"), AuthenticationScheme = "MyCookieMiddlewareInstance", AutomaticAuthenticate = true, AutomaticChallenge = true, AccessDeniedPath = new PathString("

问题 I am developing an app that used Google Authenticator. For this scenario, The web application generate QRCode via Google Authenticator. And than i read this QRCode to generate OTP via Google Authentication in mobile app. I use below code to create OTP. When i check this created OTP is always wrong. I use Google Authenticator mobile app to check my OTP is correct or wrong. Any one can help me? - (NSString *)generateOTPWithCounter:(uint64_t)counter { CCHmacAlgorithm alg; NSUInteger hashLength =

问题 I'm following the client side authentication as described at https://developers.google.com/accounts/docs/OAuth2UserAgent I am routinely signed on to multiple Google accounts. Normally, the flow will prompt me to choose which account I want to authenticate with. However there are sometimes instances where it assumes the first account I signed in with, which is not the account I wish to use. When users register with my service, they do so with a specific email address (and google id). How do I

问题 It seems that Google has disabled the old way of sending cookie SID to their Google Data Services, specifically Google Reader. This way does not work at least for me: //create request NSString* content = [NSString stringWithFormat:@"accountType=HOSTED_OR_GOOGLE&Email=%@&Passwd=%@&service=ah&source=myapp", [loginView username].text, [loginView password].text]; NSURL* authUrl = [NSURL URLWithString:@"https://www.google.com/accounts/ClientLogin"]; NSMutableURLRequest* authRequest = [

问题 I've been implementing Firebase authentication in my Android app and have got it working easily & successfully (signed in debug) for different authentication providers such as Google, however Facebook will not play ball. I'm consistently receiving a com.google.firebase.FirebaseException when trying to authenticate with Facebook. I'm using the example from the firebase/quickstart auth app on github. As you can see from the output below, the Facebook authentication is successful and a valid

问题 Here I downloaded the source code (tutorial from Google) authorization via Google. If you run a debug version everything works as planned. But if you install and run the release version, it does not work in the emulator or on a real phone. Tell me what's the problem? Maybe the problem with SHA1. When I do "gradle" -> "signingReport". I get the following: Variant: releaseUnitTest Config: none ---------- Variant: debugUnitTest Config: debug Store: C:\Users\******\.android\debug.keystore Alias:

问题 I have a problem with nodemailer where the user receive the email with sent from my google account which used to authenticate gmail instead of the alias used in mail options. Below is my code: var smtpTransport = nodemailer.createTransport({ service: config.mailer.options.service, auth: { user: "xxxx@gmail.com", pass: "password" } }); var mailOptions = { to: user.email, from: 'Test Email <aaa@aaa.com>', subject: subject, html: emailHTML }; smtpTransport.sendMail(mailOptions); Now when the

问题 Question: How do you work around the bug outlined below? Overview: I have three (3) types of unique (non-anonymous) authentication available for my app. Email/Password Google Facebook App Behavior (steps to reproduce error): In the initial sign in, no error is thrown. App saves the initial sign in method programmatically. Clear data of App from within Android Settings. Secondary sign in, the following errors (or none) are thrown. Clear data again of App from within Android Settings. Tertiary

问题 I'm developing mobile first app, using Firebase Auth. Firebase recommends redirect instead of popup. However, I can't seem to find any example of retrieving errors on using Oauth providers (facebook ,Google). Firebase has an example of handling error in SignwithPopup , but fore redirect it only states: This error is handled in a similar way in the redirect mode, with the difference that the pending credential has to be cached between page redirects (for example, using session storage). 回答1: