In Google console API manager, if I click on "Credentials", a popup comes up up stating "Failed to load service accounts."
If I dismiss that and then try to "add credentials" and select "Oauth 2.0 Client ID" I get another popup that says "A required resource is not available."
When I dismiss that, the underlying page has an exclamation icon and says "Failed to load".
This happening to anyone else? Just started failing this morning.
It looks like it may have been a temporary block. I was having the same issues earlier today, but this afternoon I was able to get past the warning messages. I didn't do anything special outside of refreshing the page (which I did try earlier) and the errors didn't come up, leading me to believe there was some service disruption, but status.cloud.google.com only reported a Google Compute Engine issue.
Related
I've created an app using react native and which is using an IdentityServer 4 server to for authentication. I'm using react-native-app-auth to perform the authentication.
When I click login the app tries to open the Identity Server login page in Safari and iOS shows a standard dialog to say:
"myApp" Wants to Use "myIdServerUrl" to Sign In.
The problem is, where it should say myIdServerUrl, it actually says (null) as you can see in the screenshot.
Does anyone know why this might be? I'm not sure if its something I've misconfigured on the app side or something I'm not sending back from IdentityServer that I should be. I would have thought it would have just shown the URL that I'm requesting but that's not the case as the login page opens correctly when I click continue, so I haven't provided a null URL or anything.
If anyone knows where iOS looks when populating this dialog that would be a great help.
Thanks a lot!
EDIT
After a bit more investigation I've found that a CONNECT request is made to the Identity Server before showing the dialog. This suggests to me that the data it's using is somewhere in the certificate as the CONNECT request is where an SSL connection is requested for HTTPS sites. I'm still not sure what field I'm missing though. I have the Subject Alternative Name populated so I'm not sure what else it could be looking for.
EDIT
It seems, if the URL has a recognizable top-level domain, the domain name (as defined here) will be reported by the dialog. For example, some.host.name.zw will be referred as name.zw and video.google.co.uk as google.co.uk.
Otherwise, ("null") is produced, as in case of some.host.name.local, etc.
It is still an empirical finding, I don't have any official reference to this, but one that is easy to test.
I have spent a lot of time lately trying to link MS VSTS account with Dialogflow. Unfortunately all my attempts failed and I am unable to find out the reason for this.
What I have done so far is:
Went to registered new VSO application (https://app.vsaex.visualstudio.com/app/register), filling in the correct callback URI (https://oauth-redirect.googleusercontent.com/r/MY_PROJECT_ID) also defining the proper scopes.
Got back to Google's action console overview page (https://console.actions.google.com/project/MY_PROJECT_ID/overview/accounts) to fill in the details for the newly created application (authorize URL, token URL etc.) selecting Authentication Code grant type.
Went to Dialogflow to set the "sign in required" for the welcome intent.
Update the action and got the "It looks like your account is not linked yet" message in simulator, but after using the DEBUG URL to complete the process, I received "account linking failed" message for no obvious reason.
I have also tried the linking procedure with 2 other OAUTH providers and it was working flawlessly, but the MS implementation apparently is not standard.
How do I go about troubleshooting login problem with the Microsoft Graph API?
I'm using the new nodejs-connect-rest-sample on node 6.9.1, and used the quick-start page to generate and an AppID. After pressing the "Connect to Microsoft Graph" button, and choosing my normal Hotmail account for login, I'm redirected to an error page saying:
We're unable to complete your request
Microsoft account is experiencing technical problems. Please try again later.
What's the next step in troubleshooting this sort of error?
The error page URL actually contains a query string with a more detailed explanation than the displayed web page does... In my case: https://login.live.com/err.srf?lc=1033#error=invalid_request&error_description=The+provided+value+for+the+input+parameter+'redirect_uri'+is+not+valid.+The+expected+value+is+'https://login.live.com/oauth20_desktop.srf'+or+a+URL+which+matches+the+redirect+URI+registered+for+this+client+application.&state=a9SlXZGisoIQrPQUbDHX732izad7LJzM
The login.live.com page should be able to display this more detail description, but currently fails to, but I'm going to mark this answered as far as a "next step", because I found I could correct the problem by changing the redirect URL registered for the app.
I've got the v2 API working in our iOS app, but have run into one issue with the login page that comes up. If a user taps the "Return to App" button, they get a page that says
Error: invalid_client
Under the Show Error Details disclosure it says
state=ok
Looking at the logs, it looks like tapping that link causes the view to try and load
https://api.box.com/oauth2/authorize?state=ok
Which then produces that screen. According to the v2 docs, we're supposed to leave the redirect_uri field in the app's entry on box.com's site empty. I'm not sure if this is a configuration issue, or whether I need to be doing something more in our app to handle that tap.
Thanks. We will be removing that shortly.
iOS app: - I am integrating google+ API in my iPhone application, i downloaded google+ API through this link:- "https://developers.google.com/+/mobile/ios/sdk/google-plus-ios-sdk-1.0.0.zip".
I have successfully integrated it in my code, but when i am trying to get user information, it is giving me error "The operation couldn’t be completed. (Daily Limit for Unauthenticated Use Exceeded. Continued use requires signup.)",
Any idea about this..!! Why this error comes.?
It says "All API calls require either an OAuth 2.0 token or an API key."
So you should get an API key and pass it as a parameter
https://www.googleapis.com/plus/v1/activities/z12gtjhq3qn2xxl2o224exwiqruvtda0i?key=YOUR-API-KEY
This issue happens when you are already logged in and still try to login again and again. I faced same error so did some experiments
1) I opened website on my mobile and everything was fine.
2) Then i tried on another laptop and used different gmail account to login and it again worked fine.
3) On my first laptop i tied again by clicking "Signin" button i got same error, so i opened google.com then logged out completely and then tried again, this time it worked.
So i believe, Issue is clicking login button again and again without logout.
I am not sure if this is a really a issue, but atleast this is what i found. I am still trying, trying and trying , will post if i found anything else.
Cheers !!