<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>OpenID Connect - Tag - GoToGuy Blog</title><link>https://gotoguy.blog/tags/openid-connect/</link><description>OpenID Connect - Tag - GoToGuy Blog</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Mon, 11 Jan 2021 14:08:05 +0000</lastBuildDate><atom:link href="https://gotoguy.blog/tags/openid-connect/" rel="self" type="application/rss+xml"/><item><title>Protect Logic Apps with Azure AD OAuth - Part 2 Expose Logic App as API</title><link>https://gotoguy.blog/2021/01/11/protect-logic-apps-with-azure-ad-oauth-part-2-expose-logic-app-as-api/</link><pubDate>Mon, 11 Jan 2021 14:08:05 +0000</pubDate><author>Jan Vidar Elven</author><guid>https://gotoguy.blog/2021/01/11/protect-logic-apps-with-azure-ad-oauth-part-2-expose-logic-app-as-api/</guid><description>This blog article will build on the previous blog post published, Protect Logic Apps with Azure AD OAuth – Part 1 Management Access | GoToGuy Blog , which provided some basic understanding around authorizing to Logic Apps request triggers using OAuth and Access Tokens.
In this blog I will build on that, creating a scenario where a Logic App will be exposed as an API to end users. In this API, I will call another popular API: Microsoft Graph.</description></item><item><title>Protect Logic Apps with Azure AD OAuth - Part 1 Management Access</title><link>https://gotoguy.blog/2020/12/31/protect-logic-apps-with-azure-ad-oauth-part-1-management-access/</link><pubDate>Thu, 31 Dec 2020 10:55:23 +0000</pubDate><author>Jan Vidar Elven</author><guid>https://gotoguy.blog/2020/12/31/protect-logic-apps-with-azure-ad-oauth-part-1-management-access/</guid><description>Azure Logic Apps are great for creating workflows for your IT automation scenarios. Logic App workflows can be triggered using a variety of sources and events, including schedules, but a popular trigger is using a HTTP trigger for starting the Logic App workflow interactively or on-demand from outside the Logic App.
To trigger a Logic App using a HTTP trigger, you need to know the endpoint URL, for example:
This URL consist of the endpoint address of the Logic App and workflow trigger, and with the following query parameters:</description></item><item><title>Blog Series - Power'ing up your Home Office Lights: Part 3 - Using Logic Apps to Authorize and Get Access Token using Oauth and Hue Remote API</title><link>https://gotoguy.blog/2020/12/04/blog-series-powering-up-your-home-office-lights-part-3-using-logic-apps-to-authorize-and-get-access-token-using-oauth-and-hue-remote-api/</link><pubDate>Fri, 04 Dec 2020 11:15:45 +0000</pubDate><author>Jan Vidar Elven</author><guid>https://gotoguy.blog/2020/12/04/blog-series-powering-up-your-home-office-lights-part-3-using-logic-apps-to-authorize-and-get-access-token-using-oauth-and-hue-remote-api/</guid><description>This blog post is part of the Blog Series: Power&amp;rsquo;ing up your Home Office Lights with Power Platform. See introduction post for links to the other articles in the series:
[https://gotoguy.blog/2020/12/02/blog-series&amp;mdash;powering-up-your-home-office-lights-using-power-platform&amp;mdash;introduction/ ](https://gotoguy.blog/2020/12/02/blog-series---powering-up-your-home-office-lights-using-power-platform---introduction/ )
Now that we have registered the application for Hue Remote API, and stored the client Id and Secret in Azure Key Vault, we can start build the Logic App that will authorize and get access token via Oauth2.</description></item></channel></rss>