[lyo-dev] Fwd: [OSLC/oslc-adapter-jama] Oauth returning "invalid_expired

[Andrii Berezovskyi <andriib@xxxxxx>]

Likely a bug in our OAuth code or abandoned Google OAuth lib.

--
–Andrew.

Vidarebefordrat brev:

Från: JasonBrownPDX <notifications@xxxxxxxxxx>

Ämne: [OSLC/oslc-adapter-jama] Oauth returning "invalid_expired_token" when using common scribejava oauth 1.0a (#11)

Datum: 14 mars 2019 17:41:10 GMT

Till: OSLC/oslc-adapter-jama <oslc-adapter-jama@xxxxxxxxxxxxxxxxxx>

Kopia: Subscribed <subscribed@xxxxxxxxxxxxxxxxxx>

Svara till: OSLC/oslc-adapter-jama <reply+0000fcde6d04e1d4a83a592cf5ddb2b789c2e29f0468047892cf0000000118a2543692a169ce191a5d30@xxxxxxxxxxxxxxxx>

When using this OSLC adapter in conjunction with ScribeJava, I have been advised that validly signed Oauth1.0a requests are returning "invalid_expired_token" (I am not an OAuth expert and did not confirm this)

ScribeJava is being actively used with other OSLC industry leader tools in the same environment.
https://github.com/HubSpot/scribe-java

Q: Is there a way to confirm if Oauth 1.0a works?
Q: Any ideas on why the common library (stable) has trouble?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.