On Thu, Aug 1, 2019 at 11:05 AM Samitha Chathuranga
wrote:
>
>
> On Tue, Jul 30, 2019 at 12:03 PM Malintha Amarasinghe
> wrote:
>
>>
>>
>> On Tue, Jul 30, 2019 at 11:56 AM Samitha Chathuranga
>> wrote:
>>
>>> Hi all,
>>>
>>> *Problem:*
>>>
>>> The objective of this task is to allow updating
On Tue, Jul 30, 2019 at 12:03 PM Malintha Amarasinghe
wrote:
>
>
> On Tue, Jul 30, 2019 at 11:56 AM Samitha Chathuranga
> wrote:
>
>> Hi all,
>>
>> *Problem:*
>>
>> The objective of this task is to allow updating the authorized field of
>> an API for a particular user through the Publisher REST
Hi Sanjula,
Thanks for the response. Please see my comments below.
On Wed, Jul 31, 2019 at 2:18 PM Sanjula Madurapperuma
wrote:
> Hi Chanaka,
>
> On Mon, Jul 29, 2019 at 11:04 AM Chanaka Fernando
> wrote:
>
>>
>>- According to the diagram, we integrate with this 42Crunch security
>>
The design review was held and the following conclusions were made.
-
In option 1 the size of the package is increased due to the ballerina
dependencies and we also have to build the docker image.
-
In option 2, with the init container present, every time the
microgateway
Hi Chanaka,
On Mon, Jul 29, 2019 at 11:04 AM Chanaka Fernando wrote:
>
>- According to the diagram, we integrate with this 42Crunch security
>audit platform at the time of the "design" phase. Based on our current
>implementation, at the "Design" phase, we have not added security,
>
Hi all,
Some times users have to give their credentials to smart TVs, IoT
devices, etc. Normally they are using the Resource Owner Password
Credential (ROPC) grant type to give access to those devices. But they face
some issues with this grant type in some devices like,
- Devices that have
