On Mon, Feb 23, 2015 at 4:07 PM, Amila De Silva ami...@wso2.com wrote:
Hi Samisa,
Should be compatible with IS 5.0.
With the SP I suppose?
On Mon, Feb 23, 2015 at 3:38 PM, Samisa Abeysinghe sam...@wso2.com
wrote:
Which WSO2 IS server version will API-M 1.9 support?
Thanks,
Senaka,
multiple relatioships are fine: it doesn't occur very often, and if, more
than two relations are rare.
And, yes, by all means, the ability to toggle particular collections of
relationship types on and off is extremely helpful! Similarly, the feature
that Isabelle brought up, namely
Yes, there are some SP 1 fixes, on which some KM features depend on.
On Mon, Feb 23, 2015 at 4:15 PM, Samisa Abeysinghe sam...@wso2.com wrote:
On Mon, Feb 23, 2015 at 4:07 PM, Amila De Silva ami...@wso2.com wrote:
Hi Samisa,
Should be compatible with IS 5.0.
With the SP I suppose?
Hi All,
FFI, following methods will be implemented under following connectors:
*PagerDuty Connector*
createIncident - Create a new event. (Incident is an event with type
'trigger')
getIncidentById - Get incident by the ID.
listIncidents - List incidents.
resolveIncident - Mark an incident as
Good 3D is hard to achieve ;-)
Best regards,
Frank
2015-02-23 10:55 GMT+01:00 Isabelle Mauny isabe...@wso2.com:
+1 - The relationship path is very important to highlight.
Right-click on a node, say Show Relationships , or Show Dependencies - And
then center the object and highlight the
Hi Frank,
Please find my response inline.
On Mon, Feb 23, 2015 at 11:38 AM, Frank Leymann fr...@wso2.com wrote:
Senaka,
multiple relatioships are fine: it doesn't occur very often, and if, more
than two relations are rare.
To start with I liked you thought from the beginning, but based on
On Mon, Feb 23, 2015 at 5:43 PM, Ranga Siriwardena ra...@wso2.com wrote:
Hi All,
During the API Manager Key Manager separation, we identified that we will
need to authenticate to identity components as signed in user instead of
admin user which is pre-configured in api-manager configuration.
With mutual-auth, authentication happens for particular user and user name
is send as a header for authentication. If the client is trusted and the
user is a valid user, then that user is identified as the signed in user.
Thank You.
Ranga.
On Mon, Feb 23, 2015 at 5:52 PM, Nuwan Dias
Actually in mutual authenticator we check for the certificate in the
header, which will set if only mutual auth is successful.
So idea here is since server trust the client, we trust the user.
BTW, mutual authenticator have problems with AWS elb. So this won't be able
to use in such places. So in
Hi Samisa,
Should be compatible with IS 5.0.
On Mon, Feb 23, 2015 at 3:38 PM, Samisa Abeysinghe sam...@wso2.com wrote:
Which WSO2 IS server version will API-M 1.9 support?
Thanks,
Samisa...
Samisa Abeysinghe
Vice President Delivery
WSO2 Inc.
http://wso2.com
On Mon, Feb 16, 2015
I don't think using SAML is a viable option because API Manager should work
without configuring SAMLSSO. For example, currently you can login to Store
with direct username/password authentication from the userstore connected
to AM.
If we are opting for SAMLSSO, then that means either depending on
Hi Ranga/Dulanja,
(for 1) can't we do this by sending the SAML assertion form API store to IS
side
--
With regards,
*Manu*ranga Perera.
phone : 071 7 70 20 50
mail : m...@wso2.com
___
Architecture mailing list
Architecture@wso2.org
Hi Cyril,
The reason for having 'v' symbolic link (in
http://localhost:9763/publisher/apis/v/assets?type=gadget ) to access
latest API, is to have a consistency across all the places where REST API
endpoints are used.
For example, in places where URL pattern matchers are implemented this
Hi Samisa,
Please find the document link from [1]. We are updating [1] in each
milestone..
And IS integration as KM fully testing is depend on completing the feature
[2] which is targeted to milestone 2..
[1] https://docs.wso2.com/display/AM190/WSO2+API+Manager+Documentation
[2] [Architecture]
Hi Shevan,
We have already put the Gmail related scenarios on hold until the Gmail
connector is ready.
i.e. *Retrieve selected messages from Gmail API (where the client has
reported the incidents) and create an incident in PagerDuty API* will be
implemented once the new Gmail connector is
+1 - The relationship path is very important to highlight.
Right-click on a node, say Show Relationships , or Show Dependencies - And
then center the object and highlight the relationships.. Now, I am going to
complicate this, but… This really calls for 3D :D - Let the user rotate
graph ..
Which WSO2 IS server version will API-M 1.9 support?
Thanks,
Samisa...
Samisa Abeysinghe
Vice President Delivery
WSO2 Inc.
http://wso2.com
On Mon, Feb 16, 2015 at 4:23 PM, Amila De Silva ami...@wso2.com wrote:
Hi All,
With API Manager 1.9.0, capability will be provided to plug in an
Hi Lasantha,
No, that capability will still be there. Plan is to write a custom grant
type (similar to client_credentials) which can accept the token validity
period as an input parameter. The API Store will invoke the endpoint which
implements this grant type.
Thanks,
NuwanD.
On Tue, Feb 24,
Hi,
I am in the progress of implementing the blocking functionality in call
mediator. Now the call mediator synapse syntax is changed to cater the
above requirement.
The synapse configuration for the call mediator blocking functionality
(blocking=true)
call blocking=true
endpoint
On Mon, Feb 23, 2015 at 5:43 PM, Ranga Siriwardena ra...@wso2.com wrote:
Hi All,
During the API Manager Key Manager separation, we identified that we will
need to authenticate to identity components as signed in user instead of
admin user which is pre-configured in api-manager configuration.
20 matches
Mail list logo
