Protect APIs in API Management using Azure Active Directory

Поделиться
HTML-код
  • Опубликовано: 16 янв 2025

Комментарии • 13

  • @xuhongliu537
    @xuhongliu537 Год назад +1

    really great demo, whole process explained perfectly

  • @papidulzuratravel8715
    @papidulzuratravel8715 2 месяца назад

    That’s a great video!!!

  • @darryltaylor9282
    @darryltaylor9282 10 месяцев назад

    This is an excellent overview. I'm shocked how much information you packed into 30 minutes. I'd love to see a more detailed one hour version using Postman as the client.

    • @AzurePowerLunch
      @AzurePowerLunch  10 месяцев назад +1

      Gla dyou liked it. Just need to find the time.

  • @aniketmhala7299
    @aniketmhala7299 Год назад

    wonderful explanation.

  • @papidulzuratravel8715
    @papidulzuratravel8715 4 месяца назад

    Amazing thanks ❤

  • @stind001
    @stind001 9 месяцев назад

    Nice explanation!

  • @weblogic7723
    @weblogic7723 11 месяцев назад

    Where was the issues obtained from ? In the video it was just pasted.

  • @MightyVigilius
    @MightyVigilius 11 месяцев назад

    nice tutorial! But what if I want the app/client to be able to call AAD and get a token without having to authenticate the user?

  • @Harsh-se1gx
    @Harsh-se1gx Год назад

    Can I get the token with postman?

  • @adityakalburgi1548
    @adityakalburgi1548 Год назад

    I am getting security recommendation as API endpoints in azure api management should be authenticated. I have openai as backend & I dont want to use Azure AD. How should I resolve this issue using other self service setup other than Azure AD. Can you please guide me on this?

    • @ianwanjala8621
      @ianwanjala8621 11 месяцев назад

      you can use the api key based authentication to protect your apis. Just go to the api section, select the api and then click on settings. Tick the option for subscription and approvals and you'll get what you are looking for.

  • @cloudbaud7794
    @cloudbaud7794 2 месяца назад

    it is not quite correct
    to call it a "Developer" portal. this is the Consumers Portal. because folks who are creating the APIs and publishing it to APIM or Azure Portal are also developers. but they are Producers. and the third entity is the API admin - who in large org are a separate persona. They typically dont know or dont have the bandwidth to know and understand the business context each of the APIs