On Sat, Mar 28, 2020 at 2:00 AM Janak Amarasena <[email protected]> wrote:
> Hi Mevan, > > In the swagger, I saw that there is a POST call with content-type support > for application/*xml *as well in addition to application/json. Why do we > need to have an *xml *content-type support? > Since we decided to support xml content type for IDP REST API, we thought to provide the same capability when creating IDP templates as well. > > Best Regards, > Janak > > On Mon, Mar 23, 2020 at 5:17 PM Mevan Karunanayake <[email protected]> wrote: > >> Hi all, >> >> I am currently working on introducing a REST API to manage identity >> provider templates. Identity Provider Template Management API is a new >> improvement to Identity Provider Management REST API [1] to keep frequently >> used identity provider configurations as templates. TemplateManager [2] >> backend OSGi service has been used to list, retrieve, add, update and >> delete identity provider templates. >> >> In order to cater the API requirements, following changes were introduced >> to TemplateManager OSGi service. You can find the PR in [3]. >> >> - Introduce four default method definitions to TemplateManager >> interface >> - update, delete and retrieve templates by ID >> - list templates using template types. >> - Use existing ConfigurationManager [4] OSGi service to implement >> TemplateManagerService. >> - Add new method definitions to ConfigurationManager service. >> - retrieve and delete resources by ID. >> >> Defined API endpoints are as follows; >> >> - API endpoint for listing identity provider templates and creating >> API templates >> >> *api/server/v1/identity-providers/templates* >> >> >> - API to retrieve, update and delete identity provider templates by >> ID. >> >> *api/server/v1/identity-providers/templates/{template-id}* >> >> >> You can find the swagger definition for above endpoints in [5]. >> >> Highly appreciate your thoughts on this. >> >> *References* >> [1] https://app.swaggerhub.com/apis/emswbandara/IAM_IDP/0.1.1 >> [2] >> https://github.com/wso2/carbon-identity-framework/blob/master/components/template-mgt/org.wso2.carbon.identity.template.mgt/src/main/java/org/wso2/carbon/identity/template/mgt/TemplateManager.java >> [3] https://github.com/wso2/carbon-identity-framework/pull/2827 >> [4] >> https://github.com/wso2/carbon-identity-framework/blob/master/components/configuration-mgt/org.wso2.carbon.identity.configuration.mgt.core/src/main/java/org/wso2/carbon/identity/configuration/mgt/core/ConfigurationManager.java >> [5] >> https://app.swaggerhub.com/apis/emswbandara/IAM_IDP/0.1.1#/Template%20management/getIDPTemplates >> >> Regards, >> -- >> *Mevan Karunanayake* | Software Engineer | WSO2 Inc. >> (m) +94712028954 | (e) [email protected] >> <https://wso2.com/signature> >> _______________________________________________ >> Iam-dev mailing list >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/iam-dev >> > > > -- > *Janak Amarasena* | Senior Software Engineer | WSO2 Inc. > (m) +94777764144 | (w) +94112145345 | (e) [email protected] > > > <https://wso2.com/signature> > _______________________________________________ > Iam-dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/iam-dev > -- Sathya Bandara Senior Software Engineer Blog: https://medium.com/@technospace WSO2 Inc. http://wso2.com Mobile: (+94) 715 360 421 <+94%2071%20411%205032>
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
