First, there should be a way of sending byte[] via JMS broker.
Then we can use the binary mapper to convert Siddhi events to byte[] and
send that to JMS broker via JMSPublisher.java.
Please let me know if this did not work.
On Tue, Oct 24, 2017 at 10:58 AM, Kalaiyarasi Ganeshalingam <
Hi all,
Currently I'm working on the unit testing for siddhi-io-jms.In the
handleCarbonMessage(Object payload)[1] method, I tried to write the test
case for payload instanceof Byte[] [2] condition.Can you give an idea to
solve this issue?
[1] https://github.com/wso2-extensions/siddhi-io-
Hi Malithi,
If you wanted to re-scan the QR code then you have to deselect the Enable
TOTP claim in the dashboard, this will automatically remove the secret key
claim from the user profile.
BTW, for both local user and federated user this will work once you
de-select the Enable TOTP claim from
Hi Vanji,
We dont have this capability of exporting them directly to CSVs. But we
have exported analytics tables to csv file with mysql command and generated
graphs etc when we do issue analysis. Following is one sample command.
SELECT * FROM IDN_OAUTH2_ACCESS_TOKEN_BAK INTO OUTFILE
Hi Vanji,
Please see my comments inline.
On Tue, Oct 24, 2017 at 5:36 AM, Vanjikumaran Sivajothy
wrote:
> Hi team,
>
> What are the positive signals that send to API Fault Summary Data from
> below fault occurrences?
>
> 1) Fault Happen in GW
>
This event tracked from fault
Hi Isura,
I don't have the specific file with me now as this was reported around
month ago.
But I directly used the UI as shown the screen shot to add the userstore.
And the userstore is a JDBC userstore on ORACLE.
Thanks,
On Mon, Oct 23, 2017 at 11:07 PM, Isura Karunaratne
Hi All,
I was using $subject to associate federated identity over google and
facebook to the local user while configuring SMSOTP and TOTP as the second
factor authentication mechanism.
As I noted, for this to work I had to configure the federated claim, as the
userAttribute in the authenticator
Hi team,
In WSO2 APIM Analytics, is it possible to export the analytics data into
CSV/Excel for given stats?
Example
Fetch API latency statistics into CVS file.
Best regards,
Vanji
___
Dev mailing list
Dev@wso2.org
Hi team,
What are the positive signals that send to API Fault Summary Data from
below fault occurrences?
1) Fault Happen in GW
2) Failure response from Backend(4XX/5XX HTTP Error Code)
3) Explicit Fault generation within GW
Best Regards,
Vanji
___
Dev
Hi Team,
I noted that we need to specifically configure server hostname and port
while configuring some IS connectors like SMSOTP and TOTP. Can't we use
placeholders instead?
Meanwhile *@IAMTeam*, if we are shipping connectors OOTB, I think we need
to have updated configs as well. Both, SMSOTP
Hi Team,
I configured two step authentication with google federated authentication
and TOTP for a service provider; i.e, first step is configured to use
google as federated IdP, second step is TOTP.
Both 'authenticationMandatory' and 'enrolUserInAuthenticationFlow' is set
to true in TOTP
Hi Denuwanthi,
I tried to reproduce the issue [1], but I couldn't. Please upload the
user-store config file used to create the secondary user store for further
analysis?
[1] https://wso2.org/jira/browse/IDENTITY-6449
--
*Isura Dilhara Karunaratne*
Associate Technical Lead | WSO2
Email:
On Mon, Oct 23, 2017 at 5:24 PM, Darshana Gunawardana
wrote:
> Hi Harsha,
>
> If the endpoint definition, or internal SPIs going to be changed, we have
> to deprecate the existing implementation as the general rule.
>
> But in this case, we still have the same functionality
Hi Harsha,
If the endpoint definition, or internal SPIs going to be changed, we have
to deprecate the existing implementation as the general rule.
But in this case, we still have the same functionality exposed with
different underlying implementation and this really don't have any SPIs
On Mon, Oct 23, 2017 at 4:42 PM, Sagara Gunathunga wrote:
>
>
> On Mon, Oct 23, 2017 at 4:36 PM, Harsha Thirimanna
> wrote:
>
>> Hi Dev,
>>
>> Since we have new DCR/DCRM endpoint with new CXF implementation, shall we
>> remove the old endpoint and impl from
On Mon, Oct 23, 2017 at 4:36 PM, Harsha Thirimanna wrote:
> Hi Dev,
>
> Since we have new DCR/DCRM endpoint with new CXF implementation, shall we
> remove the old endpoint and impl from the new release rather than
> depreciating it and update the migration documentation based
Hi Dev,
Since we have new DCR/DCRM endpoint with new CXF implementation, shall we
remove the old endpoint and impl from the new release rather than
depreciating it and update the migration documentation based on that ?
Because we are doing the unit testing improvement on top of all the
component
Updated the ticket!
On Mon, Oct 23, 2017 at 3:38 PM, Thanuja Jayasinghe
wrote:
> Hi Chamara,
>
> SAML service provider UI uses the same admin service to add sp
> configurations. So theoretically this should work.
>
> So can you please attach the SOAP request used to create the
Hello,
I have an inbound endpoint calling a sequence once triggered. In this
sequence, I call a REST API which can return a 404 causing the whole
sequence and subsequences to stop. But the return of the API is useful and
I would like to continue the process with it even if it is a 404.
Have you
Hi Chamara,
SAML service provider UI uses the same admin service to add sp
configurations. So theoretically this should work.
So can you please attach the SOAP request used to create the SAML2 service
provider?
Thanks,
Thanuja
On Sun, Oct 22, 2017 at 10:19 PM, Chamara Ariyarathne
Hi all,
Please find the documentation link for the latest release below. Sorry for
the inconvenience occurred.
Documentation
https://docs.wso2.com/display/EI611/
Thanks.
On Sat, Oct 21, 2017 at 3:27 AM, Heshitha Hettihewa
wrote:
> Hi all,
>
> The WSO2 Integration team is
21 matches
Mail list logo