Frank Kilcommins

My feedback

  1. 154 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    40 comments  ·  Azure Active Directory » B2C  ·  Flag idea as inappropriate…  ·  Admin →
    Frank Kilcommins supported this idea  · 
  2. 7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  API Management » Developer portal  ·  Flag idea as inappropriate…  ·  Admin →
    Frank Kilcommins supported this idea  · 
  3. 14 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  2 comments  ·  API Management » Developer portal  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Frank Kilcommins commented  · 

    What even is the status of 'Applications' within Azure APIM? It seems only a fake door implementation that does not really do anything currently.

  4. 32 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  2 comments  ·  API Management » Developer portal  ·  Flag idea as inappropriate…  ·  Admin →
    Frank Kilcommins supported this idea  · 
    An error occurred while saving the comment
    Frank Kilcommins commented  · 

    This would be great. And the ability both ways would be even better. In my case, we've created a central provision hub for registering users for our Apps and also for customer developers leveraging APIM. If we had the ability to write information back into APIM regarding their auto registered client that would allow them to self-serve within the Developer Portal

    Please provide an update on the review status

  5. 443 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  18 comments  ·  API Management » Developer portal  ·  Flag idea as inappropriate…  ·  Admin →
    Frank Kilcommins supported this idea  · 
    An error occurred while saving the comment
    Frank Kilcommins commented  · 

    Any update?

  6. 12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  2 comments  ·  API Management » Security  ·  Flag idea as inappropriate…  ·  Admin →
    Frank Kilcommins supported this idea  · 
    An error occurred while saving the comment
    Frank Kilcommins commented  · 

    This should be a basic requirement. We really have a strong business case to allow users registered in different identity stores (e.g. Azure AD and Azure AD B2C) to be able to authorize a client app to consume resources on their behalf.

    Most enterprises exposing APIs in today's world have internal and external consumers. Often both internal and external users use the same client applications. It seems very strange that you can't have a single API representation using multiple OAuth 2.0 / OpenID Connect providers.

    It goes against API industry best practices of having high levels of re-usability and being able to have a single API Management instance acting as a central API repository.

    Registering different APIs to simply be able to leverage different OAuth providers is not an option as this forces additional work on the client applications. Not to mention creating a very dirty overview of one's API suite.

    Please provide an update on this. Check out the Azure Bot Applications where you can leverage multiple OAuth providers.

  7. 111 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  5 comments  ·  API Management » Security  ·  Flag idea as inappropriate…  ·  Admin →
    Frank Kilcommins supported this idea  · 

Feedback and Knowledge Base