When will old apps have the scope parameter enabled?

30 posts / 0 new
Last post
Alex Andreae's picture
Joined: 2011-07-23
Aug 22, 2012
When will old apps have the scope parameter enabled?

I asked this in the thread below, but I think it got lost among other posts:
https://developer.linkedin.com/comment/17560#comment-17560

Can someone from LinkedIn tell us when the new scope parameters ever be rolled out to existing (old) apps? Since a different LinkedID member ID is generated for the same user on different apps, it's not as simple as just swapping Apps for everyone.

Can you please let us know what is the rollout period for the new scope permissions to older apps?

We need to know as we are the developers of a LinkedIn add-on for the Joomla Content Manangement System (CMS). It's currently used on thousands of Joomla powered websites, which means there are thousands of sites with the 'old' apps on them that we support. We have a release coming out that will support the new scope parameter and ability to fetch email and other fields using it. However, we need to have the right message to send to our customers on how to support the new email fields, or at least, when it will be supported.

More information about our app can be found at:
http://www.sourcecoast.com/jlinked/

Again, creating a new app isn't really an option as there's no way to 'link' the old Member ID from one app to a new Member ID from a new app. If I'm wrong here, just let me know. Otherwise, please let us know when it's possible to upgrade old apps to new apps without getting a new App ID / Key.

Thanks,
Alex

Jacob Beasley's picture
Joined: 2012-04-23
Aug 22, 2012

I also have this question. We have over 600 users on Field Nation with the ability to login with their LinkedIn accounts. We want that to continue to work, but we also want to request permissions to post status updates to their LinkedIn profiles for recommendations and positive feedback that technicians receive on our marketplace. Facebook and Twitter have already been integrated, but we are having trouble with LinkedIn. It seems the only way to fix it was to create a new application, which we are concerned will break our old functionality.

Adam Trachtenberg's picture
LinkedIn Employee
Joined: 2011-06-30
Aug 22, 2012

We will provide a transition path to let developers using the older key move to Member Permissions, which let you get email address. I don't have a date right now, but let me circle back with the team to see what we can share.

Stefan Roesch's picture
Joined: 2011-12-06
Aug 23, 2012

+1. We need to keep the app-specific member id's the same.

I did try creating a sample new app to test scope and email works there, but viewing phone numbers of your 1st degree connections doesn't work anymore even with all relevant permissions ('r_fullprofile r_emailaddress r_contactinfo r_network')

Jacob Beasley's picture
Joined: 2012-04-23
Aug 23, 2012

Hello Adam. If we regenerate a new API key for an existing app, will that allow us to take advantage of the new permission features without having to create a new app? The problem with creating a new app is that it will change the userids returned from LinkedIn, which will break some of our features. We will be launching our next iteration on the 7th of October, so please provide a solution by then for us as we have thousands of users who will use this feature to market themselves on LinkedIn.

John Whelan's picture
Joined: 2011-12-28
Aug 23, 2012

I use the Joomla LinkedIn app mentioned above. The ability to migrate seamlessly from the old app to the new one is much needed.

Adam Trachtenberg's picture
LinkedIn Employee
Joined: 2011-06-30
Aug 23, 2012

I am still working to get a migration date. But, you are correct that if you create another API key, your access grants will not transfer, and you will have different member ids. Best to wait until a formal process is available.

We know this is important, and many people are waiting on it, but we didn't want to hold up the new features while this got worked out.

Jacob Beasley's picture
Joined: 2012-04-23
Aug 24, 2012

Thank you for the response, Adam!

If existing apps can't take advantage of the new features and existing apps constitute the majority of the apps on the market, wouldn't releasing these new features with no way for existing apps to take advantage of them make the new features far less valuable? Obviously, you're the successful author with an Ivy League MBA and a history as an all around smart guy, but what was the strategy with releasing these new features but then not having a path for existing apps to implement these features?

Thanks again! We are looking forward to using these new and exciting features! Please keep us updated!

Adam Trachtenberg's picture
LinkedIn Employee
Joined: 2011-06-30
Aug 24, 2012

In case I wasn't clear earlier, it's not that we didn't think about this. However, since we use agile development techniques, we were able to finish the code for new apps first because, until it works for new apps, there's nothing to migrate to.

So, then the question was whether to hold up the entire release until the migration code was completed. Our strategy was to decide it was better to get this out now for new apps and feedback instead of holding the code internally. That not only lets new people start using this ASAP, but also lets us see if there are any gaps we might have missed that could cause us to update our migration path to be even better.

Thanks for the feedback.

Alex Andreae's picture
Joined: 2011-07-23
Aug 29, 2012

Any update on this? I understand it may not be ready to roll out yet, but an update on the timeline would be great.

Thanks,
Alex

Chris Potter's picture
Joined: 2011-03-03
Aug 29, 2012

still nothing for me even with a new api key?

Bryce Drennan's picture
Joined: 2012-03-07
Sep 5, 2012

Will this be a week? a month? several months?

Stefan Roesch's picture
Joined: 2011-12-06
Sep 5, 2012

Looking forward to using LinkedIn for our signup flow but need the email feature for old apps.

Any update? Thanks!

Adam Trachtenberg's picture
LinkedIn Employee
Joined: 2011-06-30
Sep 5, 2012

Without making any firm commitments, we are shooting for this to be ready around October 1st. Things may change between now and then, but I didn't think the wide range of uncertainty was healthy. So, I wanted to give some general guidance. I'll come back if it looks like this not be the case.

Stefan Roesch's picture
Joined: 2011-12-06
Oct 10, 2012

Any more updates here? Very much wanting to launch our login with linkedin

Thanks!

Jacob Beasley's picture
Joined: 2012-04-23
Oct 10, 2012

We just gave up and created a new app key. It means all of our old data is invalidated, but we did not want to wait months to be able to launch our software.

Kamyar Mohager's picture
LinkedIn Employee
Joined: 2012-04-04
Oct 10, 2012

Hey folks, I can assure you it won't take months! :) The migration is happening soon and we'll give an update once it happens. Sorry it's taken longer than we anticipated - there was more work involved than initially planned.

Hang tight!
Kamyar

Alek Slater's picture
Joined: 2010-08-16
Oct 24, 2012

Any progress with this? I just got rejected from Apple because of it.

Shikha A. Sehgal's picture
LinkedIn Employee
Joined: 2012-07-27
Oct 24, 2012

Sorry about that. Please hang in there, you will here back on this migration soon!

Alek Slater's picture
Joined: 2010-08-16
Oct 24, 2012

Sorry, actually let me rephrase that. Obviously Apple don't care if we have scope or not in our permissions! :D But, they do appear to have issues with the Login page for pre-scope LinkedIn Apps.

I've started another thread to avoid changing the topic here:
https://developer.linkedin.com/forum/rejected-apple-due-login-page

Jonathan Ingram's picture
Joined: 2012-06-25
Oct 24, 2012

I'm commenting on this thread as I'm waiting for this feature too but it doesn't seem possible to subscribe to threads here.

Hamish Ogilvy's picture
Joined: 2010-07-26
Oct 31, 2012

Hey Adam, any word on this? We have an app in a 50/50 state with many old users in Limbo. We need to make a decision on what to do soon, so any update on timing would be greatly appreciated.

Jacob Beasley's picture
Joined: 2012-04-23
Nov 1, 2012

It does not seem that LinkedIn is planning on getting this feature done. It has been over a month since they said they were hoping to get it done (Adam said he was hoping for October 1st), and we have heard nothing from Adam. I would act as if they have no plans of getting this feature done.

Adam Trachtenberg's picture
LinkedIn Employee
Joined: 2011-06-30
Nov 1, 2012

Sorry for not looping back sooner. The feature has been done for a bit, but because we know how critical authentication is to your application, we wanted to work even harder than usual to ensure there were no bugs or unexpected issues with the migration.

So, we've been running a suite of tests and working with a few developers on the side to pilot to feature. Unfortunately, getting everything lined up took longer than expected. But we're on the tail end of this now, and I can firmly say that we have are nearing the finish line in the next week.

Thanks for your patience and understanding.

Stefan Roesch's picture
Joined: 2011-12-06
Nov 5, 2012

Are we close? Need any more testers?

Kamyar Mohager's picture
LinkedIn Employee
Joined: 2012-04-04
Nov 8, 2012

Hi everyone,

We're happy to announce that we've released the option to opt-in your API key to take advantage of member permissions (including being able to fetch email address). This document will help guide you through the migration:

https://developer.linkedin.com/documents/member-permissions-migration-guide

Thanks to everyone for their patience and continued support of our platform!

- Kamyar

Rajesh Kasani's picture
Joined: 2011-09-14
Dec 2, 2012

Hi kamyar,
So now i can use my old API keys to get the new email permissions and the user Id will be the same as that are generated by the old keys(when i retrieve user profile).
please specify if i am wrong.
Regards,
Rajesh kasani.

Shikha A. Sehgal's picture
LinkedIn Employee
Joined: 2012-07-27
Dec 3, 2012

hey Rajesh:

You are right, you can follow the steps described in our member permissions migration guide to migrate your old API keys to newer ones which will let you use the scope parameters for email address. There will be no change to your user Ids.

Joined: 2013-04-01
Apr 4, 2013

If we opt-in our old API key to take advantage of member permissions, are we still using OAuth 1.0? Also will the "Sign-in with LinkedIn" pop window change to the new format?

Kamyar Mohager's picture
LinkedIn Employee
Joined: 2012-04-04
Apr 4, 2013

Hi Lai,

Yes, you can still use OAuth 1.0a even after upgrading your API key to use member permissions. The login dialog will change to the new format, displaying the member permissions you're requesting from the user.

Thanks
Kamyar