Hi Menaka, As we are rewriting the services, I am *not* in favor of writing SOAP services and then Carbon UI on top of it.
Given the current circumstances, I would leave the REST API. thanks, Dimuthu On Tue, Feb 13, 2018 at 2:49 PM, Menaka Jayawardena <men...@wso2.com> wrote: > Hi all, > > I'm working on implementing the Retryable Outbound Provisioning for > Identity Server. I have completed the backend implementation and now > working on developing the UI. > > As per our initial discussion, the new UI was planned to be added to the > IS carbon console. But when looking into this, I faced the following > blocker. > > The backend services of the feature are exposed as REST APIs which need > authorization header to be set. > Authorization : Bearer Base64Encoded(username:password) > > But in carbon ui, we do not use rest APIs and we also could not authorize > the rest request. So without developing a SOAP service, we could not use > the existing rest API from the carbon ui. > > I also looked at the IS dashboard. But there also, we have used only SOAP > APIs. > > Is there a method to use this without writing a WSDL for current identity > server version? > > Thanks and Regards, > Menaka > > -- > *Menaka Jayawardena* > *Software Engineer - WSO2 Inc* > *Tel : 071 350 5470 <071%20350%205470>* > *LinkedIn: https://lk.linkedin.com/in/menakajayawardena > <https://lk.linkedin.com/in/menakajayawardena>* > *Blog: https://menakamadushanka.wordpress.com/ > <https://menakamadushanka.wordpress.com/>* > > -- Dimuthu Leelarathne Director, Solutions Architecture WSO2, Inc. (http://wso2.com) email: dimut...@wso2.com Mobile: +94773661935 Blog: http://muthulee.blogspot.com Lean . Enterprise . Middleware
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture