Skip to Main Content
Forums

APEX

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

possible 18.1 BUG in LinkedIn Sign-In

Mahmoud_RabieJun 17 2018 — edited Jun 18 2018

Hello Everybody

APEX Version:

18.1

Goal:

LinkedIn Sign-in

Authentication Scheme Settings

Screen Shot 1439-10-03 at 10.14.52 PM.png

Problem:

Screen Shot 1439-10-03 at 10.16.28 PM.png

Important note on Debug (Credits to Pavel)

select message_timestamp,message

from apex_debug_messages

where application_id = 155477

and message like '%access%'

order by message_timestamp desc

gives the following result

| MESSAGE_TIMESTAMP | MESSAGE |
| 17/06/18 10:23:50.800922 م +00:00 | JSON POST https://www.linkedin.com/oauth/v2/accessToken request got HTTP status 400 |

Demo

https://apex.oracle.com/pls/apex/f?p=155477:9999

Official LinkedIn documentation

Authenticating with OAuth 2.0

@"Carsten Czarski-Oracle"

@"Dimitri Gielis"

I would appreciate any help.

Regards

Mahmoud
This post has been answered by Christian Neumueller-Oracle on Jun 18 2018
Jump to Answer

Comments

Adding in @"Christian Neumueller-Oracle" ...

1 person found this helpful
Answer

Hi,

Linkedin requires client_secret as POST parameter for the token request. This does not conform to the OAuth2 standard (see https://tools.ietf.org/html/rfc6749#section-4.3.1) and is currently not supported. I filed bug #28199613 for this issue.

Regards,

Christian

Marked as Answer by Mahmoud_Rabie · Sep 27 2020
1 person found this helpful
Mahmoud_Rabie

Carsten and Christian,

Thanks a lot.

Is there any suggested workaround to log in with a LinkedIn Profile and grasp its data?

Hi Mahmoud,

sorry, no workaround right now.

Regards,

Christian

1 person found this helpful
1 - 4
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Jul 16 2018
Added on Jun 17 2018
#apex-discussions
4 comments
329 views