Re: [Architecture] [APIM] REST API Support for Dynamic SSL Certificate Installation Feature.

Hi Isuru, The certificate will be added to the nodes that are configured in Environments in the api-manager.xml. If there is a gateway cluster, only the manager node trust store will be updated. So we need to sync the trust store and the sslprofiles.xml file among the other nodes in the cluster.

Re: [Architecture] [APIM] REST API Support for Dynamic SSL Certificate Installation Feature.

Hi Menaka, In this feature, if there are a more than one Gateway nodes, how do we handle the trust store synchronization across those? Sorry about the extremely late question. On Wed, Jul 11, 2018 at 5:32 PM, Menaka Jayawardena wrote: > Hi, > > I had an offline discussion with Sanjeewa and

Re: [Architecture] [APIM] REST API Support for Dynamic SSL Certificate Installation Feature.

Hi, I had an offline discussion with Sanjeewa and Malintha regarding the rest API convention of using uuid instead of certificate alias. But, for this feature, if we adopt the UUID approach, there will be a DB level modification and method signature changes. In the current approach, the

Re: [Architecture] [APIM] REST API Support for Dynamic SSL Certificate Installation Feature.

On Tue, 10 Jul 2018, 14:40 Sanjeewa Malalgoda, wrote: > In our REST API design we keep using UUID to represent path to atomic > resource. Sometimes even we had unique attribute we still used auto > generated UUID. If we are using alias to identify resource within resource > collection we are

Re: [Architecture] [APIM] REST API Support for Dynamic SSL Certificate Installation Feature.

In our REST API design we keep using UUID to represent path to atomic resource. Sometimes even we had unique attribute we still used auto generated UUID. If we are using alias to identify resource within resource collection we are deviating from that convention. So i think we need to think about

Re: [Architecture] [APIM] REST API Support for Dynamic SSL Certificate Installation Feature.

Hi Mushthaq/ Fazlan, Thank you very much for the suggestions. I have used the resource path as* '/certificates/{alias}/info'* because it's self-explanatory. The main objective of the API (the initial thought) is to get the status of the certificate. (Whether it is expired or not and the expiry

Re: [Architecture] [APIM] REST API Support for Dynamic SSL Certificate Installation Feature.

Hi Menaka, DELETE is expecting alias in a query param and GET is expecting it to be passed in a path param. I think modifying DELETE as DELETE certidicates/{alias} and GET as GET certificate/{alias} is more Restful. On Tue, Jul 10, 2018 at 12:09 PM Menaka Jayawardena wrote: > Hi, > > I'm

Re: [Architecture] [APIM] REST API Support for Dynamic SSL Certificate Installation Feature.

Hi Menaka, Is there any particular reason for making the path as '/certificates/{alias}/info' to get the certificate details rather than going for the path '/certificates/{alias}'? Thanks & Regards, Mushthaq On Tue, Jul 10, 2018 at 12:09 PM Menaka Jayawardena wrote: > Hi, > > I'm working on

[Architecture] [APIM] REST API Support for Dynamic SSL Certificate Installation Feature.

Hi, I'm working on implementing a REST API for the Dynamic Certificate Installation feature for API Manager. (User stories ) The current implementation only supports add, retrieve and delete