Linked in integration authentication error - ios

I have performed the steps described above on LinkedIn Web site is authenticated and try the sample application Any help would be appreciated. The purpose is to verify the application I use LinkedIn to build credentials
I have executed the steps as mentioned on the LinkedIn website for authentication and trying out the sample app getting error...
failed for URL: "linkedin: // authorize" - error :
"This app is not allowed to Query for scheme linked"

Please show some code related to your question ...
Have you added your bundle identifier in LinkedIn developer account ?
Have you set application transport security related things in .plist URL scheme ?

Related

react-native auth0 sign in with apple?

How to sign in with apple in react-native using auth0 web form authentication?
Tried following this guide: https://auth0.com/docs/connections/apple-siwa/set-up-apple?_ga=2.267694410.553381554.1591475612-866095660.1584309547
But no luck. Testing the connection gives me: invalid_redirect_uri.
One problem with guide was this part about creating service id:
"After checking Sign In with Apple, click on Configure and define your Web Domain (example.com) and your Return URL. Make sure that your Return URL is your Auth0 domain, such as foo.auth0.com (or your Auth0 custom domain if you have one) and follows this format: https://YOUR_AUTH0_DOMAIN/login/callback. "
Since I use react-native, the callback is not an url that starts with 'https', but a custom uri to return users back to the application. Apple won't allow me to put that custom uri when creating the service-id, but requires the https prefix.
Has anyone succeeded in implementing sign in with apple for react-native applying the auth0 web authentication? Any help is appreciated.
Just as I decided to ask, I got this solved.
Problem was that I was just copy-pasteing the login callback from my auth0 app's configuration directly. Instead of actually doing what reads in the guide.
So I changed the login callback to just follow this format: https://YOUR_AUTH0_DOMAIN/login/callback
And it works now.

google action account linking Accounts failed to link

I want to account for linking google action to my web app. followed the OAuth Client Information. I have implemented
Set Up an OAuth2 Server Using Passport in Laravel( tutorial link).Where I did authentication. finally, I find my application at my home mobile app but when goes to click on MY created app it gives me account linked and after that an error "something went wrong and close" but when I open my
it gives me an error
Accounts failed to link. Please close your browser and try again
The documentation at Add authentication to your project indicates that you need to use the Authorization Code auth type instead of the Implicit flow.

Okta authentication failing in iOS App with valid details

I am trying to authenticate with Okta in my iOS app, Create a app is Okta dashboard and added client id and redirect url's. After setting up and installing app in simulator. app is throwing the below error:
Please let me know if i missed any settings.
Created a native app from dashboard.
It looks like the client ID you're sending in the request is not what you think it is. You should be able to copy the URL from your browser, paste it in something like Notes, and examine the client ID. Make sure it matches what you have in your Okta org and that it doesn't contain any unexpected characters in it.
That's a common problem being faced by every newbie.
Here are some steps which will guide you to make your Okta authentication without error.
Create an application in Okta Page.
At text field & you may put your domain id. ex dev-xxxx.okta.com:/callback
Provide the same detail in your okta.plist in iOS Application.
You may refer to the Okta 'GitHub Repositories' for working samples.
Thanks.

Custom scheme URIs are not allowed for 'Web' client type - Google with Firebase

I am trying to implement google sign in using firebase in to my iOS app. I follow this tutorial.
https://firebase.google.com/docs/auth/ios/google-signin
I have setup the iOS app in firebase and use the google clientID and reversedClientID from the dowloaded GoogleService-Info.plist.
FYI: I have a custom sign-in button instead of the google sign in button. Anyway when i click the sign in button, google following error display in a webview.
I know my problem is the same as which described in this question.
Google 400 Error: invalid request Custom scheme URIs are not allowed for 'Web' client type
But, in my case, I have created the app in Firebase still I get the error. Any idea please...
The first step is to check if you have already the OAuth 2.0 ID for iOS. To do this please open the Credentials page in the API Console. I hope you will find iOS client for your application under OAuth 2.0 client IDs section. If not, please follow this Guide
The second step is to replace the Web Client ID with in iOS Client ID from OAuth 2.0 client IDs section. To do this, you should open the GoogleService-Info.plist and modify following keys: CLIENT_ID with [value].apps.googleusercontent.com and REVERSED_CLIENT_ID with com.googleusercontent.apps.[value].
if you're using flutterfire ui package you need to change the client id parameter in your GoogleProviderConfiguration class with the iOS client id,
you can copy it from here Credential page
example:
providerConfigs: [
GoogleProviderConfiguration(
clientId: "your copied key here"),
]
re-build you're app and you should be good to go
I've just faced this same issue using flutterfire_ui on Flutter.
The error appears to be from a couple of things. As Valeriy points out you need the ios client ID. But I still got the error if I used the scopes
openid
"https://www.googleapis.com/auth/userinfo.email",
"https://www.googleapis.com/auth/userinfo.profile",
Instead change these to
openid
email
profile
Strangely the opposite is true for Android, where the WebID and the first of the scopes should be used.
It also pays to be aware of the OAuth Content Screen..
In google cloud go to APIs & Services > OAuth consent screen > Edit.
You can add scopes here and fix any missing required fields that Firebase might not be filling out (I had 1). I believe this takes a while to propagate after a change, so give it an hour.

Change Facebook developer account for an iOS app - bundle identifier

I've developed an iOS app that is integrated with Facebook to allow users to log in using their FB accounts. That works fine.
The app is also supposed to use a web service developed by another company. Said web service also uses Facebook integration.
Both my app and the web service were developed using different Facebook developer accounts. Now it seems a major problem I've got needs both of these to be part of the same "Facebook application" which means they'd have to belong to the same Facebook developer account.
I asked the other company's developer to add a native iOS aspect to his Facebook app, gave him my app's bundle ID and received a Facebook app ID and secret in return. I made the appropriate changes to my app's Info tab in XCode - the bundle ID is the same one that I gave him, the FacebookAppID is the one I got from him and so is the URL Schemes thing (with an "fb" preceding the actual FBAppID).
However, when I try to log in using Facebook credentials in the app, I constantly get com.facebook.sdk error 2 which is explained in the console by this message: FBSDKLog: System authorization failed:'The Facebook server could not fulfill this access request: remote_app_id does not match stored id '. This may be caused by a mismatch between the bundle identifier and your app configuration on the server at developers.facebook.com/apps.
Is there a step I'm missing in this transition of app between FB developer accounts? Could something else be the cause of the problem here? If my question is off-topic, please at least point me in the direction where I could get some answers.
Indeed - it turned out that the problem was exactly what the error message said: the bundle ID was different for both the application in XCode and in the Facebook developer account; that was because the developer from the other company made a spelling mistake (lower case instead of upper case letter) in the bundle ID.

Resources