The official documentation says:
Click on the My Apps link in the top navigation menu to manage your
LinkedIn applications.
From here, you can create a new application if you don't already have
one, or view the details of your existing applications. You will find
your API Key value listed in the section named "OAuth Keys".
But the application pages has been probably changed without updating documentation because there is no "OAuth Keys" section at all.
Anybody knows where the API key can be found?
Yeah, I came across that too. It's actually called "Client ID", not "API key". Look under your App profile in the Authentication section
Related
I've tried this with several MS accounts that have Azure/AAD accounts in place and have attempted using both Visual Studio 2015 as well as 2017 and am getting the exact same bug/error.
Using the default ASP.NET MVC template with AAD integration out of the box (no code changes at all). The App is registered in my AAD account, and I see the tenantId and other GUIDs are in the Web.Config as they should be. I also traced the call stack as far as I could and the tenantId is initialized properly yet I still get this error:
Requested tenant identifier '00000000-0000-0000-0000-000000000000' is not valid. Tenant identifiers may not be an empty GUID.
This happens after the permissions acceptance screen.
Here is a screenshot as well:
As requested, here is the Web.Config:
So the resolution was very simple. But this is not documented anywhere, not even in Vittorio Bertocci's book on the subject - which leads you to believe that you can log in as the Azure subscription owner after creating the Visual Studio project without any additional setup in Azure.
Since the new portal is in preview the UX is not really all that obvious. Here are the steps to take after creating a new ASP.NET project with Active Directory integration:
You have to log into Azure (in the new portal)
Click on Active Directory.
Go to your "App Registrations"
You will see your new application there. click on it.
Inside of the "Essentials" panel at the top of the app registration blade you will see a link with the header "Managed application in local directory" and the link will have the same name as the blade you are already in (This is the confusing part). Click on that link...
You are now one blade deeper and are able to see how many users this application has. It will likely be 0. - This is the issue!
Click on "Users and Groups" in the menu on the left side and you can start adding users.
Please note that the above steps may change as AAD comes out of preview in the new portal.
I'm creating a web application to manage text books. There is only 1 person who can add, remove, or edit the existing items in the database. this is my first ever asp.net web app and I've researched where to edit privileges and cant seem to find it anywhere. I am using the built in register/login feature of asp.net. I need to have 1 admin account and the rest be basic users with only read access. Could anyone lead me in the right direction?
If you are referring to asp.net Identity, here is a "getting started" article:
https://www.asp.net/identity/overview/getting-started/adding-aspnet-identity-to-an-empty-or-existing-web-forms-project
I'm trying to follow this tutorial for Google's Analytics API.
The tutorial says "If you haven't already registered your application with the Google Developers Console, then set up a project and application in the Developers Console".
The documentation for the Developers Console says "A project consists of a set of applications...", which makes sense.
I'm able to create the project, but I don't see any way to create an application within that project. Both pieces of documentation linked above instruct me to click on "Registered apps" in the left sidebar, but there is no such link. (I believe these docs were written for an older version of the Console.)
On the recommendation of another poster, I tried using the old Console instead, but I can't find any "Registered apps" link (or any other way to create an application) in that version, either.
Any ideas?
You didn't say whether you were doing this as a service account, web app, or installed app but this should get you pointed in the right direction for all of those.
And, Google radically changed the console UI.
The application gets created when you create the credentials for an application type.
If you created the project in the Google Console, select the project and follow the instructions in the tut you linked to:
Go to the Google Developers Console.
Select a project.
In the sidebar on the left, select APIs & auth. In the displayed list of APIs, make sure all the APIs you are using show a status of ON.
In the sidebar on the left, select Credentials.
Add this step: Click on the "Create New Client ID" button then select the application type.
In either case, you end up on the application's credentials page.
To find your application's client ID and client secret, and set a redirect URI, expand the OAuth 2.0 Client ID section.
Write down the values for each of these fields:
Client ID
Client secret
It is said you cannot create apps automatically with the current facebook API.
Create and Configure Facebook Apps via API
How to programatically create a Facebook application via JS SDK or Open Graph API? (createApplication)
Yet woobox.com does it.
I have created a few photo contests in their portal. It didn't ask for extra permission. No dialogs showed up. I just got these links:
http://www.facebook.com/pages/-/105892812908965?sk=app_422118604517529&app_data=dlt-1
http://www.facebook.com/pages/-/105892812908965?sk=app_451684954848385&app_data=dlt-1
How did they create these apps?
app_422118604517529
app_451684954848385
I would expect
www.facebook.com/pages/-/105892812908965?sk=app_SAME_APP_ID&app_data=WOOBOX_ID_1
www.facebook.com/pages/-/105892812908965?sk=app_SAME_APP_ID&app_data=WOOBOX_ID_2
You are correct with the presumptions that Facebook apps/users/groups and pages can't be created dynamically. What woo box is what many other page tab applications are doing. They create a number of applications for different templates and then customize them according to your inputs. They don't create apps dynamically. And these dynamic apps get their required data from app_data field.
Another point to note is
An app can't be installed on a page twice
that is why many Service provider that provide page tab applications maintain a pool of applications to fulfill their user's desires.
We are working to integrate one of our client's existing accounting system into Google App. Eventually we need to list it on Google App Marketplace.
Here is what we have already done:
Downloaded the sample .NET app available from Google - this one
Created a vendor profile on the Google Apps Marketplace
Listed our test application on the Google Apps Marketplace
So far we have ONLY been able to authenticate the user using DotNetOpenAuth.
We are struggling with following issues:
Unable to access the Calendar Data API and display the next appointment. We are getting 401 Unauthorized when querying the Calendar Data API.
To access the Calendar Data API we need to have a ConsumerKey & a ConsumerSecret - which is made available ONLY after you submit your application for Approval.
We submitted the app for approval to get a ConsumerKey & a ConsumerSecret although its just a pilot app that we are building first. We don't want that app to be published as of now but we could not find a way to keep that listing private and available ONLY for dev & testing purpose as of now.
We have placed the ConsumerKey & ConsumerSecret in the sample marketplace app but even now we get a 401 Unauthorized access while quering the Calendar Data API.
We have already spent 2-3 days trying to find proper documentation for this and get it to work but in vain. Any help / guidance to get it to work and also keep the listing private in dev mode until we are ready, would be really appreciated.
Here is the modified 2 page source code i am trying to run.
There are some key misconceptions in your post.
Your keys are already available to you. Open Marketplace, click on "My Vendor Profile" top right, and look right under the listing, below the stars: View OAuth Consumer Key link is there. If it isn't, you did not mark your app as an installable one. To fix that, create a new app entry, and make sure you provide a valid manifest.
To test your new app, BEFORE you submit your app for approval, open the Marketplace page for it and click the Add it now button. You will be offered a field to enter the Google Apps domain name to test with.
Only domains you add your app to will be accessible with the marketplace key.
Chances are if you sort these two things out things will start working :)