I feel that, having a configuration file for authentication / authorization
gives us more control over selecting the authentication mechanisms.
In current IS, it uses is a rest-auth framework [1] which looks for a
configuration file to see whether a certain resource is protected or not.
I think
+1 Isuru, that would be extremely helpful I think. The search functionality
should respect user boundaries to ensure that APIs that should not be
visible to a given user don't get exported.
On 17 January 2017 at 21:51, Isuru Haththotuwa wrote:
> Hi Rushmin/Uvindra,
>
> Thanks
Yes it will be much more user-friendly, if we can allow the providers to
search and export.
In implementation POV we can use the functionality to export all APIs for a
providers etc .. by searching in a controlled manner.
e.g. calling a /export-all resource (by a provider) would call this search
Hi all,
Now there is a working model of $subject.
*Features : *
- Can add WebSocket ServerEndpoints in OSGi environment dynamically.
- Support for @PathParam annotation
- Server push support
These are the decisions made after the code review.
- Migrate WebSocket Session
Hi All,
We had a review meeting of the implementation of MSF4J Filter
Configuration. Mentioned below is a brief explanation of how MSF4J Filter
Configuration works.
*Notes: *
- We have decided to improve the current interceptor implementation
rather than following the JAX-RS filters
Hi,
@CEP team : Appreciate your response about this matter.
Thanks,
Nisala
On Mon, Jan 16, 2017 at 2:14 PM, Nisala Nanayakkara wrote:
> Hi All,
>
> According to the off-line discussion that we had with Suho, Chandana,
> Kishanthan, Udara, Tanya and Tharik on CEP requirements
Hi Rushmin/Uvindra,
Thanks for the clarifications and inputs.
Yes I agree that there is a valid use case for bulk import of APIs. This
was suggested in a previous reply as well, by Jochen. I suggest we use the
standard API search functionality to cater this, where we can use all the
supported
I think there might be a valid case for allowing a provider to
export/import all the APIs that belong to that provider only in bulk. Its
much more user friendly as Rushmin has mentioned
On 17 January 2017 at 17:15, Rushmin Fernando wrote:
> Hi Isuru,
>
> Please see my comments
Hi Thanuja,
On Tue, Jan 17, 2017 at 10:42 AM, Thanuja Uruththirakodeeswaran <
thanu...@wso2.com> wrote:
> Hi Sajith,
>
> Can we consider this tool also for migrating APIs from previous versions
> to latest version?
>
>
No, this tool is to export / import API s across different environments
only,