AFAIU the problem we are addressing isn't browser to web app authentication
but web app to server authentication when webapp trying on some backend
work. Travelocity is used for a POC I guess.
Any way have we done any implementation here. Can you post some link for
that. And I guess we are not
Hi Keerthika,
That approach looks so good since we can use this even in the past releases
also. As I remember Thulasika used similar approach before.
*Nadeeshaan Gunasinghe*
Software Engineer, WSO2 Inc. http://wso2.com
+94770596754 | nadeesh...@wso2.com | Skype: nadeeshaan.gunasinghe <#>
Hi ,
I am planing to do the siebel REST connector using a Siebel 15.0.0.0.
I have decided to implement following operations for Siebel Objects using
[1] :
-
query particular record by row ID.
-
delete particular record by row ID.
-
insert the row.
-
upset
Hi Rajjaz,
The diagram makes me bit confused. The concept is: IS allows the user to
access the requested application (here travelocity.com), If it
authenticates him with other API (here X509 certificates app).
Are we adding the certificate to the client via authenticator and
authenticate that
Hi Dimuthu,
I'm here attached the image[1] shows the flow of X509 certificate. and X509
certificate is going to be a one of custom authenticator. SSL is by far the
largest use of X.509 certificates, many people use the terms
interchangeably. They're not the same however; a "SSL Certificate" is a
Hi All,
This is my understanding and correct if I am wrong.
An X.509 certificate contains information about the identity to which a
certificate is issued and the identity that issued it.
We can configure this authinticator even as the first step.
So for each user there is a going to be a
I think best is first check with script mediator and if there are
performance issues will move to class mediator approach.
On Sat, Jan 30, 2016 at 12:56 PM, Keerthika Mahendralingam <
keerth...@wso2.com> wrote:
> +Nadeesan.
>
> On Sat, Jan 30, 2016 at 12:48 PM, Keerthika Mahendralingam <
>
+Nadeesan.
On Sat, Jan 30, 2016 at 12:48 PM, Keerthika Mahendralingam <
keerth...@wso2.com> wrote:
> +1 for class mediator.
>
> @Thulasika, As Malaka said in the code review, it is better to create a
> common module for this function so that other connectors also make use of
> it.
>
> On Sat,
+1 for class mediator.
@Thulasika, As Malaka said in the code review, it is better to create a
common module for this function so that other connectors also make use of
it.
On Sat, Jan 30, 2016 at 12:40 PM, Kathees Rajendram
wrote:
> Hi Thulasika,
>
> I think Script mediator
Hi All,
I used the script mediator to store the access token then I tried to use
ESB 4.10 registry persistence feature to store the access token. It works
in 4.10 but It doesn't work with previous versions even we can't enable the
connector in previous versions(4.8 & 4.9) so finally I have used
Hi Thulasika,
I think Script mediator will have some performance impact on the mediation
logic. You should create a class mediator to store the content into the
registry. As Malaka said you should do load testing with both and compare
performance with script mediator and class mediator.
String
Hi Manjula,
At the moment Lochana is integrating the work we done for AS 5.3.0 and this
feature is not yet included on AS 6.0.0 which is pure Tomcat bases. You can
find the branch on [1].
Lochana will update once the initial work is included.
[1]
Hi All,
If we implement this using esb 4.10 feature whole connector is compatible
with ESB 4.10 only. Doing a separate version of each connector to support
this feature is not good.
So will proceed with script mediator approach. However we need to run some
testing before implementing this for
Hi all,
X 509 is only the certificate to verify client and server.
@shakila/malaka
according to last meeting with prabath , we need to upload the key file
manually but when we try to access the server without set the key file
there want to be pop-up window to upload the key file. and yes your
14 matches
Mail list logo