HI, Shouldn't we adhere to the existing APIs [1], [2] in Identity Server 5.x at > the moment? Otherwise, users who have written applications based on the > existing APIs won't be able to migrate easily. If I am not mistaken, C5 > based Identity Server is based on carbon-auth.
Since auth components are ships initially with APIM, migration will not be a big issue right? even for AM 3, it support IS 5.4.0 at the moment. But in further for IS or any other product need backward compatibility, product IS can support backward compatible endpoints. So that, it can be deprecated and new REST API can be introduce as new feature. Thanks and Regards On Mon, Jan 8, 2018 at 7:53 PM, Pubudu Gunatilaka <[email protected]> wrote: > Hi Malintha, > > Shouldn't we adhere to the existing APIs [1], [2] in Identity Server 5.x > at the moment? Otherwise, users who have written applications based on the > existing APIs won't be able to migrate easily. If I am not mistaken, C5 > based Identity Server is based on carbon-auth. > > [1] - https://docs.wso2.com/display/IS540/apidocs/OAuth2-dynamic- > client-registration/#!/operations#OAuthDCR#registerApplication > <https://docs.wso2.com/display/IS540/apidocs/OAuth2-dynamic-client-registration/#!/operations%23OAuthDCR%23registerApplication> > [2] - https://docs.wso2.com/display/IS540/SCIM+2.0+REST+APIs > > Thank you! > > On Mon, Jan 8, 2018 at 7:34 PM, Malintha Amarasinghe <[email protected]> > wrote: > >> - apim-group, +architecture >> On Mon, Jan 8, 2018 at 7:21 PM, Malintha Amarasinghe <[email protected]> >> wrote: >> >>> Hi All, >>> >>> The carbon-auth [1] component we are currently working on exposing a set >>> of APIs for authentication/authorization purposes. This is to propose a set >>> of base paths to be used on those APIs. >>> >>> As a convention we have been using below format when defining base paths >>> for the currently available REST APIs in API Manager: >>> >>> /api/*<product>*/*<name_of_the_api>*/v*<version>* >>> >>> eg: /api/am/publisher/v1.0 >>> >>> Below are the suggested basepaths: >>> >>> 1. Client Registration and Management REST API >>> /api/auth/dcr/v1.0 >>> >>> 2. OAuth REST API >>> /api/auth/oauth/v1.0 >>> >>> 3. SCIM REST API >>> /api/auth/scim/v1.0 >>> >>> 4. Scope Registration REST API >>> /api/auth/scope-registration/v1.0 >>> >>> 5. Token Introspection REST API >>> /api/auth/introspect/v1.0 >>> >>> >>> *Note:* I have used "auth" instead of the product name. >>> >>> Appreciate your thoughts on this. >>> >>> [1] https://github.com/wso2/carbon-auth >>> >>> Thanks! >>> Malintha >>> >>> -- >>> Malintha Amarasinghe >>> *WSO2, Inc. - lean | enterprise | middleware* >>> http://wso2.com/ >>> >>> Mobile : +94 712383306 <+94%2071%20238%203306> >>> >> >> >> >> -- >> Malintha Amarasinghe >> *WSO2, Inc. - lean | enterprise | middleware* >> http://wso2.com/ >> >> Mobile : +94 712383306 <+94%2071%20238%203306> >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > *Pubudu Gunatilaka* > Committer and PMC Member - Apache Stratos > Senior Software Engineer > WSO2, Inc.: http://wso2.com > mobile : +94774078049 <%2B94772207163> > > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Rukshan Chathuranga. Software Engineer. WSO2, Inc. +94711822074
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
