I was following the Pyrebase tutorial and I got it up and running for one user account. I added another user account to the code and now I'm getting an error saying email address isn't found. The user account has been added to the Firebase User, and given the same access as the first account.
I've confirmed that the account has been added to Firebase with the correct email and password.
user = auth.sign_in_with_email_and_password("someEmailAddress#gmail.com", "Secret Password")
I'm expecting a return code of 0, stating it's connected successfully. However, I'm getting the error below:
raise HTTPError(e, request_object.text)
requests.exceptions.HTTPError: [Errno 400 Client Error: Bad Request for url: https://www.googleapis.com/identitytoolkit/v3/relyingparty/verifyPassword?key=AIzaSyDgn6aURRvEDP-M738sy7oo0ubbNqqLXzY] {
"error": {
"code": 400,
"message": "EMAIL_NOT_FOUND",
"errors": [
{
"message": "EMAIL_NOT_FOUND",
"domain": "global",
"reason": "invalid"
I have found my error. After adding the account under the Project Overview -> Project settings -> Users and Permissions tab, I forgot to add the account under the Authentication tab on the left hand side. Once that's added, the code works as expected.
When obtaining the Endpoint from Firebase Auth REST API, pick the Endpoint for signup with email/password.
The error arises because the Endpoint is for sign in with email/password.
You will be performing a sign in operation instead of sign up hence the error email not found.
Related
I have two instancies of OpanAM. One works as OAuth2 provider, the second works as OAuth2 client.
When I enable option "Map to anonymous user" on service instance, all flow works fine - client redirects me to provider, where I enter my username and password, then it redirects me back to client where I can see my new anonimous profile.
But in my case I need to map user from provider to client when user logins to my system.
When i enable function "Create account if it does not exist" when I apply consent screen it redirects me back to client and I see this error message: "Unknown error. Please contact your Administrator".
I have enabled logs and in logs I see this error:
org.json.JSONException: JSONObject["sub"] not found.
org.json.JSONException: JSONObject["name"] not found.
org.json.JSONException: JSONObject["given_name"] not found.
org.json.JSONException: JSONObject["family_name"] not found.
ERROR: unknown callback null
When I perform REST-request to provider on userinfo endpoint with Postman it returns me this JSON:
{
"sub": "user123",
"name": "name",
"given_name": "gn",
"family_name": "fn"
}
Based on this response, I configure mapping in OAuth2 module on client OpenAM this way:
Account Mapper Configuration:
sub=sub
name=name
given_name=given_name
family_name=family_name
Attribute Mapper Configuration:
sub=sub
name=name
given_name=given_name
family_name=family_name
Thanks!
I am trying call the API https://realestate.docusign.com/restapi/v1/rooms?dateRangeType=LastUpdated&roomStatus=Open&startDate=2018-12-06
But I get error response as below:
{
"message": "Unauthorized authentication in production",
"errorCode": null
}
Since you are using realestate.docusign.com, so you are hitting PROD rooms API url, please verify if the user whose credentials you are using is active in PROD Rooms and is correctly linked with PROD Account Server and also verify if the Integrator Key is Live in PROD Account.
I keep getting a AuthenticationFailed error with a InvalidAuthenticationTokenAudience inner error when attempting to query the /environments endpoint.
I have already created an app in the Azure Active Directory, given it access in the time series insights management portal and I can already get an Oauth 2.0 Access token from the auth URL.
I have tried giving the token url the 'https://api.timeseries.azure.com/' resource/audience/scope but the API keeps returning the same error message:
{
"error": {
"code": "AuthenticationFailed",
"message": "Server failed to authenticate the request. The token has been obtained from wrong audience or resource.",
"innerError": {
"code": "InvalidAuthenticationTokenAudience",
"message": "The access token has been obtained from wrong audience or resource '00000002-0000-0000-c000-000000000000'. It should
exactly match (including forward slash) with one of the allowed
audiences 'https://api.timeseries.azure.com/'."
}
} }
I'm using Postman with the Oauth 2.0 authentication type, the client credentials Grant Type and send as basic Auth Header option for the token request.
Has anyone tried this with success?
Update 01:
The decoded (using JWT as suggested in comments) payload portion of one of the tokens shows the that the aud field is 00000002-0000-0000-c000-000000000000. Which is definitely wrong.
Based on the exception, it indicates that the resource is not matching https://api.timeseries.azure.com/ when acquire the access token.
So please make sure that the resource is https://api.timeseries.azure.com/, for more information please refer to the screenshot.
Get access token
I test Get environments API, it works correctly for me.
GET https://api.timeseries.azure.com/environments?api-version=2016-12-12
Currently we are in the process of developing one iPhone application that deals with google calendar. There was need of syncing calendar events to the server side. Everything works fine.
But for push notification , we are following this process
Whenever we post request to :
https://www.googleapis.com/calendar/v3/calendars/email#gmail.com/events/watch
with parameters
"id":Unique string ( channel id) ,
"type": "web_hook",
"address": "https://abc-api.herokuapp.com/user/notifications"
In the header , we are sending
Authorization : **Bearer 'Access_token'**
and content type : json
We already added domain as authorized domain in the google api console
Access_token is user's account access token .
We are getting "Unauthorized webhook call" error.
{
"error": {
"errors": [
{
"domain": "global",
"reason": "push.webhookUrlUnauthorized",
"message": "Unauthorized WebHook callback channel: https://abc-api.herokuapp.com/user/notifications"
}
],
"code": 401,
"message": "Unauthorized WebHook callback channel: https://abc-api.herokuapp.com/user/notifications"
}
}
Anyone here who can help us to solve the issue ?
You might want to check this post, providing solution like verifying if your domain have a valid (not self-signed) SSL license. Also in google-api-php-client GitHub, instead of setting https://example.com/google/push (resulted in Unauthorized WebHook callback channel) or https://www.example.com/google/push (allowed me to successfully open channel, and object has been returned, however webhook has not been fired) as address they tried https://www.example.com/google/push/index.php and worked.
One potential issue is if you're testing in Google's "try it" section of the documentation. It's not stated, but this particular request does not work there.
Otherwise, there are a few things that need to happen with the domain you are supplying in the address. First, you need to make sure its verified in the google developers console for the application you are hitting the api with. Additionally, you need to add the website property to your search console (even if its just an api) and verify ownership.
Also, once you get past the unauthorized address issue, you will get another error requiring a resourceId be supplied.
I'm getting the following when trying to authenticate using OAuth2 using the Java client library:
Error:
Code was 403
Msg: Forbidden
{
""error"": {
""errors"": [
{
""domain"": ""global"",
""reason"": ""insufficientPermissions"",
""message"": ""Insufficient Permission""
}
],
""code"": 403,
""message"": ""Insufficient Permission""
}
}
What could be causing this "Insufficient Permission" error?
If you are using Google Wallet Objects API, make sure that you share your Account in the Merchant Account with the Service Account Email Address (the one you got when you created your credentials - you can get this one from the cloud console https://cloud.google.com/console, the one that ends with #developer.gserviceaccount.com)
Login to the Merchant Dashboard, click on Account Management and then click on Share. Add the email to the list of users.
You'll also want to share your merchant account with any users you want to give preview access to your classes and discoverables.