meteor send email works in development mode via mailgun
then after meteor build the packaged code fails
Exception while invoking method 'forgotPassword' AuthError: Invalid login - 503 5.5.1 Error: authentication not enabled
no errors with same mailgun smtp settings in development mode ?
now it works
tests show that email.js can work with simply 'snmp://localhost:25'
however the 'account-ui-bootstrap-dropdown' does not, so it maybe an issue
with the package.
better to work directly with the api to develop login features now.
Related
Recently (within past week) our unity webgl (Unity v2019.4.16f1) application has been unable to read files using the google drive API. When I check the web console I see the following error:
UnityGoogleDrive: HTTP/1.1 403 Forbidden
Google Drive API Error Description: Code '403' Message: 'The request is missing a valid API key.'
Domain: 'global' Reason: 'forbidden' Message: 'The request is missing a valid API key.' LocationType: '' Location: ''
(Filename: ./Runtime/Export/Debug/Debug.bindings.h Line: 35)
The application has been in place for 4 months without issue until now.
We currently have an OAuth 2.0 client ID setup, but no API key as we haven't needed it before. The plugin we are using for google drive access in Unity (https://github.com/Elringus/UnityGoogleDrive) does not have any obvious settings for adding an API key in addition to the OAuth ID.
When running the application directly in Unity (which uses localhost) there are no errors and files can be accessed.
I have tried disabling and re-enabling the API in the cloud console. This has given mixed results. The initial request on the web application after re-enabling the Google Drive API succeeds without any errors. All subsequent requests fail with the same error.
Based on the missing values I thought the issue might be that we needed a valid billing plan assigned to the google project but that has not resolved the issue either.
I have tried generating an API key but I am not sure where I need to pass it in order to resolve the issue (if that is even the cause of the issue).
The error reported was a red herring. The real issue was that our request was not triggering authentication with Google. Our Unity dev environment had cached an authentication token which is why the dev environment functioned but the production app failed.
We resolved the issue by sending a request to the GoogleDriveAbout API before anything else, which seems to reliably trigger reauthentication. Once authenticated everything works as expected.
I have tested account kit sms verification on my local server and everything went right but when I push the editings on my remote server it starts to return "NOT_AUTHENTICATED" to the page in response.startus.
I have tried to use APP key and secret, that I use normally on remote server, on my local server to test if it was a problem of api version (indeed on my local I use a Facebook APP with 2.5 version and on server I use a Facebook APP with 2.2 version) but everything went right on my local server and I get the right response.status.
When I insert the sms verification code on account kit popup it told me that the number it's verified but when it closes itself I get response.status = NOT_AUTHENTICATED.
I have RHEL6 with installed Redmine 2.6. While trying to set up sending emails I got the error :
504 5.3.3 AUTH mechanism LOGIN not available
More than all, while changing the password of an account, the email came to me successfully. Hmm...
So i tried googling that trouble but that gave me no resolved issues. Please, help me to understand how to find out what is wrong. That is important !
I'm developing a website that is going to use Facebook authentication.
I'm using GWT and it works fine when I run the code compiled, but when I'm running the development it does not work.
The problem is when I'm trying to retrieve the access_token from Facebook.
I'm receiving the error below:
"error":{"message":"Error validating verification code. Please make sure your redirect_uri is identical to the one you used in the OAuth dialog request","type":"OAuthException","code":100}"
Obviously, the redirect_uri is identical as the login url one.
I found out (by this topic) that the problem is the last part of the url "?gwt.codesvr=127.0.0.1:9997".
How can I solve this? or how can I manage to use the GWT development mode with this problem?
Thanks,
Normally this is due to the url verification FB does.
When you register a new app in FB you have to configure the set of domains (App Domains) authorized to use the FB login form.
Unfortunately you cannot set 127.0.0.1 nor localhost as a valid domain, so you cannot use GWT dev-mode unless you configure a hostname in your domain pointing to your localhost.
If you set mydomain.com as a valid App Domain in your FB application, configure localhost.mydomain.com pointing to 127.0.0.1 in your local hosts file or in your DNS server. Then use http://localhost.mydomain.com:8888/myapp.html?gwt.codesvr=localhost.mydomain.com:9997 to run dev mode in your browser.
I found out the problem.
By encoding only the gwt.codesvr value it works.
However, using php urlencode function on it did not work, I had to encode it myself.
The gwt dev param ended like this "?gwt.codesvr=127.0.0.1%3A9997"
I am trying to integrate github authentication with a rails application using
omniauth-github-1.1.0 and rails-3.2.12 gems
Every time I try to authenticate my app using Github I get this error:
"OmniAuth::Strategies::OAuth2::CallbackError" with URL -
http://127.0.0.1:3000/auth/github/callback/?error=redirect_uri_mismatch
Application is registered with:
URL - http://127.0.0.1:3000
Callback URL - http://127.0.0.1:3000/auth/github/callback/
Omniauth initialzer file:
Rails.application.config.middleware.use OmniAuth::Builder do
provider :github, ENV['GITHUB_KEY'], ENV['GITHUB_SECRET']
end
I have double checked the GITHUB_KEY, GITHUB_SECRET. Can't really see any reason for authentication to fail.
I was using localhost:3000 for running the app and expecting the callback to work. But I should have used http://127.0.0.1:3000/ instead.