Hi Lasantha,
Thank you very much for the given feedback. The plugin wraps the equinox p2
director application internally to install features. However, I am not sure
what you have mentioned here is handled by the plugin. So lets have a demo
and check that out.
On a separate note there are few limi
+1 yes go ahead with Basic Authentication
On Thu, Oct 8, 2015 at 9:54 AM, Rasika Hettige wrote:
> Hi All,
>
> As John and Malaka have mentioned, can we go ahead and implement this
> connector with the Basic Authentication and later if required will
> implement
> oAuth.
>
> Thanks & Regards
> Ras
Hi All,
As John and Malaka have mentioned, can we go ahead and implement this
connector with the Basic Authentication and later if required will implement
oAuth.
Thanks & Regards
Rasika
--
View this message in context:
http://wso2-oxygen-tank.10903.n7.nabble.com/Connector-SalesforceDesk-tp126
Hi Dinusha,
The new configuration seems more intuitive and easier to use. +1 for the
proposed changes.
A minor issue that I have encountered when using the previous plugin is
that resources that are copied via the p2.inf for a feature get left in the
repository/components/features directory of th
The WSO2 UES team is pleased to announce the 4th Milestone of WSO2 UES
2.0.0.
The distribution is available at [1].
*New Features*
- Anonymous view of dashboard
- Save Gadget preferences via JS API
Please report any issues you may find in our JIRA
https://wso2.org/jira/browse/UES
carbon-d
+1 for basic auth.
OAuth is not intuitive for most people and an easy OOTB experience is what
we build our brand on.
If we find we need OAuth later on - when someone has bought it - then we
could do it then - but OOTB wins every time for me.
Sorry to intrude but I'm very passionate about the OOT
Well IMO I think if we have Basic authentication it will make the
integration simple and faster with ESB.
[1] http://dev.desk.com/API/using-the-api/#authentication
On Wed, Oct 7, 2015 at 6:08 PM, Kathees Rajendram wrote:
> Adding Vinitha.
>
> On Wed, Oct 7, 2015 at 5:31 PM, Kathees Rajendram
>
Adding Vinitha.
On Wed, Oct 7, 2015 at 5:31 PM, Kathees Rajendram wrote:
> Hi Vinitha,
>
> As Kesavan mentioned, we better to go with oAuth 1.0 rather than basic
> authentication. To implement SalesforceDesk connector with oAuth 1.0, you
> don't need to use any external Java libraries. You can u
Hi Vinitha,
As Kesavan mentioned, we better to go with oAuth 1.0 rather than basic
authentication. To implement SalesforceDesk connector with oAuth 1.0, you
don't need to use any external Java libraries. You can use HMAC-SHA1
signature generation method.
You can refer Twitter2.0.0 [1] and Amazon
Hi all,
We are hoping to introduce a revamp version of carbon-feature-plugin 2.0.0
(previously known as carbon-p2-plugin) along with Carbon 4.5.0 and Carbon
5. Following were taken into consideration when revamping the
carbon-feature-plugin.
- Optimizing the existing plugin (architecture and t
Hi All,
Methods under the following categories have been omitted, because they are
in beta version.
*Dashboard Operations
Import Operations*
Regards,
Vinitha
--
View this message in context:
http://wso2-oxygen-tank.10903.n7.nabble.com/Connector-PowerBI-tp126559p126636.html
Sent from the WSO2
Hi Kesavan,
We choose Basic Authentication instead of Oauth 1.0 due to the following
reasons;
1. For Oauth1.0, a java library has not been provided, hence we need to use
an external Java library (e.g: Signpost) to implement the Oauth flow.
2. Basic authentication is the simplest form of authentic
12 matches
Mail list logo
