Imported Google Group message.
Date:Saturday, 26 December 2015 09:41:35 UTC.
Tyk doesn't require an Authorization header to access that OAuth path on your API, I think the URL is wrong, which is triggering the access controls check in Tyk as it thinks it's a non-reserved URL.
If you did check the source, you will see the OAuth paths are added before the key check.
What URL are you using for Authorize path?
From: Adil Atilgan ad...@adilatilgan.com
Sent: Friday, December 25, 2015 14:24
Subject: I do not understand Oauth2 Flow
To: Tyk Community Support tyk-commun...@googlegroups.com
- show quoted text -
You received this message because you are subscribed to the Google Groups "Tyk Community Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firstname.lastname@example.org.
To view this discussion on the web, visit https://groups.google.com/d/msgid/tyk-community-support/df8fef2a-2d11-4e62-9b69-b8f53e0cee85%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.