Hi All, Currently I am looking into adding Rest API to achieve the same functionality. For the Rest API support of dynamic SSL based certificate, we have provided following Rest API resources to support the functionality,
*public abstract Response certificatesAliasContentGet(String alias);public abstract Response certificatesAliasDelete(String alias);public abstract Response certificatesAliasGet(String alias);public abstract Response certificatesAliasPut(InputStream certificateInputStream,Attachment certificateDetail,String alias);public abstract Response certificatesGet(Integer limit,Integer offset,String alias,String endpoint);public abstract Response certificatesPost(InputStream certificateInputStream,Attachment certificateDetail,String alias,String endpoint);* I think we can also, go with the same set of similar resources for the client certificate managerment, instead of endpoint, apiId will be used for the client certificate management usecase. Appreciate your thoughts on this. Thanks. Regards, Megala On Fri, Sep 21, 2018 at 5:16 PM Megala Uthayakumar <[email protected]> wrote: > Hi Ishara, > > On Fri, Sep 21, 2018 at 4:52 PM Ishara Cooray <[email protected]> wrote: > >> Hi Megala, >> >> "REMOVED" and "UNIQUE_IDENTIFIER" fields have been newly introduced for >> the following purposes. >> When we delete the uploaded certificate from UI, that change will not be >> immediately reflected in the gateway environment, until the user clicks on >> "Save and Publish" button. In that case, when the delete button is clicked >> for the certificate, relevant entry related with certiifcate in the >> database will not be deleted, rather that entry will be updated with the >> value "REMOVED" to true. Then the entry will be removed from the databse, >> once the changes are published to the gateway. >> Further "UNIQUE_IDENTIFIER" field was introduced, as when a API is >> authenticated against a certificate using mutual SSL, the axis context will >> only hold the certificate as a property, it will not contain the alias of >> the certificate. Hence when a mutual ssl authenticated request received in >> the gateway, "UNIQUE_IDENTIFIER" (i.e. combination of certificate serial >> number and issuer dn) will be used to check the subscription tier of >> particular certificate by making a call to key manager. Hence the >> throttling key will be {{UNIQUE_IDENTIFIER of certificate}}__{{API >> Identifier}}. >> >> +1 >> I prefer field UNIQUE_ID than UNIQUE_IDENTIFIER >> wdyt? >> > +1 from me. Will use UNIQUE_ID. > > Thanks. > > Regards, > Megala > -- > *Megala Uthayakumar *| Senior Software Engineer | WSO2 Inc. > (m) +94 779967122 | (e) [email protected] > <http://wso2.com/signature> > -- *Megala Uthayakumar *| Senior Software Engineer | WSO2 Inc. (m) +94 779967122 | (e) [email protected] <http://wso2.com/signature>
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
