Error validating client secret
Microsoft Graph is the evolvement of API’s into Microsoft Cloud Services.For me not being a developer, a key difference is interacting with with Graph API using OAuth 2.0 via Power Shell.It is also worth to mention that guidelines and instructions from Azure official document or other online articles are insufficient to follow, this is understandable because ARM supports with Azure Python SDK is fairly new (as of September 2016) and some Azure services are in ‘preview’ mode.Similar to AWS IAM service, Azure allows users to have resource access through Active Directory and Service Principal credentials which only require (encrypted) key strings such as client ID, secret Key or tenant ID instead of certificate files generated by openssl e.g. Let’s walk through SDK functions to see how it works. Getting these values is explained from here: https://azure.microsoft.com/en-us/documentation/articles/resource-group-create-service-principal-portal/ but app registrations are not described entirely because Admin consent needs to be done additionally. I've never had an issue with Facebook and socialite. Once again, the url passes in what "type" of social connection driver to keep it dynamic and setting the type in the DB. Honestly you should NEVER have to set anything in the vendor folder (it gets replaced on updates) or use other extensions/packages the instructions don't call out for. Notice the facebook array: I pull in the keys from env file, but the callback (redirect) url MUST match your settings on the facebook's developer console for the app keys your using, otherwise you'll get errors.
Depending on what you’re doing you’ll need to select the appropriate access.
Through a number of my previous posts I’ve interacted with the Graph API using client libraries such as the library.
This post details using Power Shell to talk directly to Graph API and managing Authentication and Authorization using OAuth 2.0 and Azure Web App.
If I run the app from my dev box (reply URL https://localhost:44332) I get the above error, If i run it from azure I get this error 'the page cannot be displayed because and internal server error has occurred' I cant see that ive done anything wrong here, am I missing something obvious ?
This is the third article in the Authentication with Rails series.