- 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
