API Connect

 View Only
Expand all | Collapse all

Common Oauth APIs across organization

  • 1.  Common Oauth APIs across organization

    Posted Tue April 06, 2021 05:45 AM
    Hi Folks

    Having used API connect for a few years, we have ended up deploying the same OAuth APIs in multiple catalogs as having all business APIs in a single catalog is not a viable option. While this approach works but I would have ideally liked to have one version of the OAuth API accessible globally to all catalogs. This way it would have been much each to maintain as we would have only one copy of the API code being used for authentication.

    We are using V5 and I don't think this is possible to have the OAuth api in one catalog and the business API in another. We are looking to migrate to V10 and having attended multiple sessions on V10 from IBM, I have been informed that OAuth APIs are first class citizens in V10 (though I do not understand the jargon properly).

    I would like to hear from the community how such scenarios can be handled better.


    Regards
    Vaibhav Mehra

    ------------------------------
    Vaibhav Mehra
    ------------------------------


  • 2.  RE: Common Oauth APIs across organization

    Posted Tue April 06, 2021 07:12 AM
      |   view attached
    In Both, 2018.x and v10.x versions. Yes, You can create OAuth APIs at cloud component and can share them across all organizations, If you would like have isolated oauth apis then it can be created at Manager component levels. so that each catalog have their own oauth apis.

    ------------------------------
    SESIKANTH SINGAMSETTI
    ------------------------------

    Attachment(s)

    txt
    sesikanth-reply.txt   280 B 1 version