Hi All,
In c5 carbon-deployment we have a method to manually deploy artifacts where
we only provide artifact's path and artifact type. This was no issue until
5.2.0-m3 since we only had a single deployment directory.
public void deploy(String artifactPath, ArtifactType artifactType)[1]
But since
Hi Manorama,
Do we have documentation of the scenarios that we support as part of the
initial version of the AS4 connector?
On Mon, Jul 17, 2017 at 10:06 PM, Manorama Perera wrote:
> Hi Malaka,
>
> Thanks for the suggestion. I think we can introduce a custom listening
>
Hi All,
The WSO2 Analytics team is pleased to announce the release of *WSO2 Stream
Processor Version 4.0.0 Milestone 9*.
WSO2 Smart Analytics let digital business creating real-time, intelligent,
actionable business insights, and data products which are achieved by WSO2
Stream Processor's
The WSO2 Integration team is pleased to announce the release of Enterprise
Integrator 6.2.0-M2. It is available for download now from following
location.
https://github.com/wso2/product-ei/releases/tag/v6.2.0-m2
*Tasks/Bug Fixes and Improvements*
WSO2 Jira - Fixed Issues
Hi
Proceeding with the aforementioned, we replaced carbon-logging with
pax-logging. Now it is essential to start logging bundles before other
bundles and according to the current architecture the bundles are loaded as
per the bundles.info file which are listed in alphabetical order. Hence pax
Hi Kasun,
On Thu, Aug 10, 2017 at 12:11 PM, KasunG Gajasinghe wrote:
>
> Can you list possible customer usecases on why they want to use this?
>
The main usecases are
1. If user using multiple applications which supports different
authentication protocols on same browser
On Thu, Aug 10, 2017 at 2:52 PM, Malithi Edirisinghe
wrote:
>
>
> On Thu, Aug 10, 2017 at 12:28 PM, Johann Nallathamby
> wrote:
>
>>
>>
>> On Thu, Aug 10, 2017 at 11:47 AM, Sugirjan Ragunaathan > > wrote:
>>
>>> Hi,
>>>
>>> Currently I’m
Having an AuthnDataPublisher and SLOEventPublishers seems redundant to me.
We can use our eventing framework here. An impl of AuthDataPublisher will
fire events and respective LogoutListener will act as event handlers. So
that those event handlers will pick relevant event and act accordingly.
On
On Thu, Aug 10, 2017 at 12:28 PM, Johann Nallathamby
wrote:
>
>
> On Thu, Aug 10, 2017 at 11:47 AM, Sugirjan Ragunaathan
> wrote:
>
>> Hi,
>>
>> Currently I’m working on a project 'Cross protocol single logout'. WSO2
>> Identity Server provides Single LogOut
Hi Chamila,
I'll go through that.thanks for the detail.
Regards
Krishan.
On Wed, Aug 9, 2017 at 10:15 AM, Chamila Adhikarinayake
wrote:
> Hi Krishan,
>
> There was an intern project done to introduce Event Listeners using
> observers to api manager. I think you could re-use
On Thu, Aug 10, 2017 at 11:47 AM, Sugirjan Ragunaathan
wrote:
> Hi,
>
> Currently I’m working on a project 'Cross protocol single logout'. WSO2
> Identity Server provides Single LogOut over applications, participating on
> the same session over the same authentication protocol
Can you list possible customer usecases on why they want to use this?
On Thu, Aug 10, 2017 at 11:47 AM, Sugirjan Ragunaathan
wrote:
> Hi,
>
> Currently I’m working on a project 'Cross protocol single logout'. WSO2
> Identity Server provides Single LogOut over applications,
Hi,
Currently I’m working on a project 'Cross protocol single logout'. WSO2
Identity Server provides Single LogOut over applications, participating on
the same session over the same authentication protocol and Single SignOn
over the different protocols.
[image: 1.png]
Objective:
Design and
Hi Nirthika,
Can you please add a redmine task [1] to the new changes you have done and
update the required information on this feature?
Then we can update the test cases and documentation team will be able to
update the documents as well.
[1]
14 matches
Mail list logo