ll take more
>> consideration on those matters before proceeding further.
>>
>> Thank You,
>> Dulangi
>>
>>
>> On Thu, Nov 19, 2020 at 12:43 PM Sanjeewa Malalgoda
>> wrote:
>>
>>> As I understand, mutual TLS has nothing to do with the place w
t; WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: *+94779109091*
>
--
*Sanjeewa Malalgoda*
Software Architect | Associate Director, Engineering - WSO2 Inc.
(m) +94 712933253 | (e) sanje...@wso2.com | (b) Blogger
<http://sanjeewamalalgoda.blogspot.com>, Medium
<
(m) +94766697385 | Email: dula...@wso2.com
> <http://wso2.com/signature>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
--
*Sanjeewa Malalgoda*
Software Architect | Associate
product and vote.
>
> [+] Stable - go ahead and release
> [-] Broken - do not release (explain why)
>
> Thanks,
> WSO2 API Manager Team
>
> --
> *Arshardh Ifthikar*
> Senior Software Engineer | WSO2 Inc.
>
> Email: arsha...@wso2.com
> Mobile: +94777218551
>
>>>> [1] - [APIM-3.0] Publisher rest API to check a role name existence
>>>>
>>>> Thanks & Regards,
>>>> *S.Meruja* |Software Engineer | WSO2 Inc.
>>>> (m) +94779650506 | Email: mer...@wso2.com
>>>> Linkedin: https://www.link
ptimization etc. And most
importantly we can completely decouple. I feel its something to consider
before make a decision on api. Thoughts?
>
> On Thu, Apr 23, 2020 at 12:52 PM Sanjeewa Malalgoda
> wrote:
>
>> When I looked at some other solutions I found we can do the
ew REST
> API to the analytics webapp to get the required information.
>
> Appreciate your thoughts on the above.
>
> Regards,
> Ruwini
> --
> Ruwini Wijesiri
> Senior Software Engineer,
> WSO2 Inc.
>
> Mobile : +94716133480
>
> <ht
; consider how to migrate APIs from previous versions.
>>
> We have a way to update the RXT field at runtime. For example [1]. We
> did this for all newly added RXT fields.
>
> [1] https://github.com/wso2/product-apim/issues/3525
>
>>
>> @Sanjeewa Malalgoda , @
>> Comparison of “Using existing commands” and “Using a new set of
>>> commands”
>>>
>>> Using existing commands
>>>
>>> Using a new set of commands
>>>
>>>-
>>>
>>>Advantage
>>>
>>> C
oken.
>>>>
>>>>- Generated Token from Oauth Providers contains a specific change
>>>>related to the Token.
>>>>
>>>> So two OAuth providers can co-exist (within a single tenant space) if
>>> their issued tokens can be separate
plication
>>
>>- Oauth Application will remove from Respective Oauth Provider
>>assigned.
>>
>>
>> I appreciate any thoughts and feedback on this.
>>
>
> Are we only supporting this for subscriptions within the same tenant?
>
>>
>>
>>
;>>>>>
>>>>>>>>>>>>>>> Hi all,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> We are pleased to announce the third release candidate of
>>>>>>>
isn't a
>> need of saving the other service endpoints.
>>
>>>
>>> Please go through the description and I highly appreciate your thoughts
>>> on this $subject.
>>>
>>> Thanks!.
>>>
>>>
>>>
>>> --
>>> Methusha Thu
74078049 | (w) +94112145345 | (e) pubu...@wso2.com
>>> <http://wso2.com/signature>
>>>
>>>
>>
>> --
>> *Manjula Rathnayaka* | Senior Technical Lead | WSO2 Inc.
>> (m) +94 77 743 1987 | (w) +94 11 214 5345 | (e) manju...@wso2.com
>> G
n.
>
> It would be best to release global scope feature along with the current
> scope behavior and depend on the usage we can decide whether we
> discontinue the local scope feature.
>
I think current local scope feature will be there anyway. This will come on
top of that.
Thanks
schema:
>>>> $ref: '#/definitions/Error'
>>>>
>>>>
>>>> #-
>>>>
>>>> # Update a global scope
>>>>
>>>> #--
type: string
>>>> version:
>>>> type: string
>>>>
>>>> provider:
>>>> type: string
>>>>
>>>> resources:
>>>> type: array
>>>>
>
t;
> Here we would maintain these depth-related and complexity-related values
> per API. These policy related details will be appended to the existing
> local entry which is maintained per API after encoding with base64. Then at
> the gateway level, we can read these API level policies
ities available in the
> Ballerina Central. Regarding the user groups, when the support is provided
> through the ballerina central in the future we will be able to inherit it
> as well.
>
> Thanks.
>
> On Wed, Oct 23, 2019 at 3:29 PM Sanjeewa Malalgoda
> wrote:
>
>> Hi All,
_
>>>>>> Architecture mailing list
>>>>>> Architecture@wso2.org
>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>>
>>>>>
>>>>>
>>>&
>>>>>>>>>> It is a HEAD method (*/roles/{roleName}*) which will return a
>>>>>>>>>>>> 200 status code if the given role name exists and a 404 status
>>>>>>>>>>>> code if the
>>>>>>>>>>>&g
h v3 as we are releasing a major version for APIM.
>>
>>>
>> Thank you!
>> --
>> *Pubudu Gunatilaka* | Associate Technical Lead | WSO2 Inc.
>> (m) +94774078049 | (w) +94112145345 | (e) pubu...@wso2.com
>> <http://wso2.com/signature>
>>
>>
>
g]
>
> [1]. https://blog.rapid7.com/2016/12/06/introduction-to-honeypots/
>
> Thank you and regards,
> *Nadee Poornima*
> Software Engineer - Support Team | WSO2
>
> Email : nad...@wso2.com
> Mobile : +94713441341
> MyBlog: https://medium.com/nadees-tech-stories
>
> &l
; grant type that allows you to exchange an OAuth token for a self contained
>> (JWT) token?
>>
>>>
>>> Will it be under consideration in this implementation?
>>>
>>> On Wed, Feb 13, 2019 at 12:52 AM Nuwan Dias wrote:
>>>
>>>&g
r we support a scenario like that today. What is the
> grant type that allows you to exchange an OAuth token for a self contained
> (JWT) token?
>
>>
>> Will it be under consideration in this implementation?
>>
>> On Wed, Feb 13, 2019 at 12:52 AM Nuwan Dias wrote:
o feel that we need to introduce a config to switch on
>> enabling/disabling this feature so that we can also use the microgateways
>> in the current mode.
>>
>> On Thu, Feb 7, 2019 at 3:58 PM Sanjeewa Malalgoda
>> wrote:
>>
>>> Hi All,
>>> I'm ini
deployed
micro services and send revoked JWT list.
Each of these methods will have their own advantages and disadvantages.
Lets use this mail to discuss those in detail and come to conclusion.
Thanks,
sanjeewa.
--
*Sanjeewa Malalgoda*
Software Architect | Associate Director, Engineering - WSO2 Inc.
(m
. This capability
will help us to do some additional stuff when we implement solutions. As
example we can think of generating UUID during server startup and send it
to some external system for tracking purpose.
Thanks,
sanjeewa.
--
*Sanjeewa Malalgoda*
Software Architect | Associate Director
rg
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
--
*Sanjeewa Malalgoda*
Software Architect | Associate Director, Engineering - WSO2 Inc.
(m) +94 712933253 | (e) sanje...@wso2.com | (b) Blogger
<http://sanjeewamalalgoda.blogspot.com>, Medium
<https://medium.co
in phased approach. First we will do introspection call which
validates access token. Then we can think of throttling, usage data
monitoring etc. We will create repo named
istio-apim and start our work there. If you have any suggestions to above
proposal please let us know.
Thanks,
sanjeewa.
--
*Sanjeewa
using the server push feature in the microgateway
> since there's no much use cases of it with the microgateway.
>
> Thank you
> Best Regards,
>
> *Varuni Punchihewa*
> Intern - Software Engineering | *WSO2*
> *Tel:* +94 71 699 5861
> <http://wso2.com/signature>
>
setup command is executed. If a user needs to add a custom policy, the user
>>>> can add it to the policy directory in the Microgateway.
>>>>
>>>> Your comments and suggestions on this feature will be highly
>>>> appreciated.
>>>>
>
/signature>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>
>
> --
> Malintha Amarasinghe
> *WSO2, Inc. - lean | enterprise | midd
___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
--
*Sanjeewa Malalgoda*
Software Architect | Associate Director, Engineering - WSO2 Inc.
(m) +94 712933253 | (e) sanje...@wso2.c
gt;>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> best regards,
>>>
>>>
>>> Nicolas Maujean
>>>
>>> ___
&
gt;
>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>>
>>> *Jayanie Bogahawatte*
>>> *Software Engineering Intern*
>>> WSO2 (University of Moratuwa)
>>> *mobile *: *+94 777563324* | *email *: jaya...@w
gt;> For that swagger-model-validator for Node.js can be convert in to
>>>>> Ballerina.
>>>>>
>>>>>
>>>>>
>>>>> Fig 1: Validating a request
>>>>>
>>>>>
Fig 2: Validating
>>>> a response
>>>>
>>>>
>>>> Thank you!
>>>>
>>>> --
>>>>
>>>> *Shalki Wenushika*
>>>> *Software engineering Intern*
>>>> WSO2 (University of Morat
gt; Chamila Adhikarinayake
>>> Associate Technical Lead
>>> WSO2, Inc.
>>> Mobile - +94712346437
>>> Email - chami...@wso2.com
>>> Blog - http://helpfromadhi.blogspot.com/
>>>
>>
>>
>>
>> --
>> Regards,
>> Chamil
On Wed, Sep 5, 2018 at 3:16 PM Bhathiya Jayasekara
wrote:
> Hi Sanjeewa,
>
> On Wed, Sep 5, 2018 at 1:11 PM Sanjeewa Malalgoda
> wrote:
>
>>
>>
>> On Wed, Sep 5, 2018 at 12:58 PM Wasura Wattearachchi
>> wrote:
>>
>>> Hi All,
>>>
&g
cations, you can go through the document which I have
> attached below. It will be hugely appreciated if you can provide your
> feedback.
>
>
> Until then I will analyze API Manager 3.0 more and will start writing User
> Stories.
>
>
> Thank you!
> --
>
it should return same response as get do.
Thanks,
sanjeewa
>
>> thanks,
>> Chanaka
>> --
>> Chanaka Jayasena
>> Associate Tech Lead,
>> email: chan...@wso2.com; cell: +94 77 4464006
>> blog: http://chanaka3d.blogspot.com
>>
>
>14. Expand each section of Production keys.
>15. Expand "subscribe to available application"
>16. Expand the "subscribe to a new application"
>17. Go through the express mode
>18. Go to application page.
>19. View applicatio
O2, Inc. http://wso2.com
>> email : nuw...@wso2.com
>> Phone : +94 777 775 729
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>
>
> --
> Mush
>>>
>>> *Menaka Jayawardena*
>>> Senior Software Engineer
>>> WSO2 Inc.
>>>
>>> Phone: +94 71 350 5470
>>> LinkedIn : https://lk.linkedin.com/in/menakajayawardena
>>> Blog : https://menakamadushanka.wordpress.com/
; Would appreciate your comments and thoughts on this.
>
>
> [1]
> https://github.com/wso2/carbon-apimgt/blob/master/components/apimgt/org.wso2.carbon.apimgt.rest.api.store/src/main/resources/store-api.yaml#L3668
> [2] [Dev] [APIM_REST_API] What are the properties to
e.
>
Yes, lets keep this simple for this release and improve it in future.
>
>
>> On Mon, May 28, 2018 at 5:30 PM Isuru Haththotuwa <isu...@wso2.com>
>> wrote:
>>
>>>
>>>
>>> On Mon, May 28, 2018 at 5:03 PM, Sanjeewa Malalgoda <sa
e generated. This archive will embeds bre, generated balx which
> someone can take and run without configuring anything.
> - This command also outputs APIs which have updated and commands
> which are available to run in target folder
>- *micro-gw run (wit
gt; --
>>>>> Chamin Dias
>>>>> Mobile : 0716097455
>>>>> Email : cham...@wso2.com
>>>>> LinkedIn : https://www.linkedin.com/in/chamindias
>>>>>
>>>>> ___
>>>>> Architecture m
nager 3.0 we did not introduce such a concept anyway. Are you
> suggesting we remove this from 2.x as well?
>
> On Thu, 29 Mar 2018 at 1:17 pm, Sanjeewa Malalgoda <sanje...@wso2.com>
> wrote:
>
>> Hi All,
>> In API Manager we have application access token and user a
token with write(access add photo) scope. In
oauth spec also we cannot see this type of differentiation. So considering
all these shall we remove application access token concept from API
Manager? Any limitations with this?
Thanks,
sanjeewa.
--
*Sanjeewa Malalgoda*
WSO2 Inc.
Mobile : +94713068779
+WSO2+Identity+Server
>>>
>>> Thank you!
>>> --
>>> *Pubudu Gunatilaka*
>>> Committer and PMC Member - Apache Stratos
>>> Senior Software Engineer
>>> WSO2, Inc.: http://wso2.com
>>> mobile : +94774078049 <%2B94772207163&g
<https://stackoverflow.com/questions/tagged/wso2-am>
Reporting Issues
We encourage you to report issues, improvements and feature requests
regarding WSO2 API Manager through WSO2 API Manager GIT Issues
<https://github.com/wso2/product-apim/issues>.
~ WSO2 API Manager Team ~
--
*San
enabled, at the point of generating API synapse
>configuration, we can add the schema to a local entry which the name of the
>local entry will be UUID + api+ resource version.
>- We can add a property to hold the local entry name related with UUID
> and add a class mediator
t
>>> [3] https://docs.google.com/document/d/1Ls0VuLsJaQtQAPgR3Nkw
>>> trcbFUvVZuPW_gXA7bV5mmo/edit?usp=sharing
>>>
>>> Thanks.
>>>
>>> Regards,
>>> Megala
>>> --
>>> Megala Uthayakumar
>>>
>>> Seni
ed. Therefore
> we are planning to use following response format.
>
> HTTP/1.1 200 OK
> {
> "numberOfMessagesDeleted": 0
> }
>
>
> On Thu, Mar 8, 2018 at 10:41 AM, Sanjeewa Malalgoda <sanje...@wso2.com>
> wrote:
>
>> If purging is handle by
;>>> Hi Eranda,
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Jan 10, 2018 at 6:47 PM, Eranda Rajapakshe <eran...@wso2.com
>>>>>>> > wrote:
>>>>>>>
>>>>&
lt;https://wso2.com/signature>
>>>
>>
>>
>>
>> --
>> *Pamod Sylvester *
>>
>> *WSO2 Inc.; http://wso2.com <http://wso2.com>*
>> cell: +94 77 7779495 <077%20777%209495>
>>
>
>
>
> --
>
; RESTful design guidelines and usability in mind.
>> Thanks
>>
>> On Tue, Feb 13, 2018 at 11:28 AM, Sanjeewa Malalgoda <sanje...@wso2.com>
>> wrote:
>>
>>> It looks like claims are attributes of dialect. In that case when user
>>> create/update
2018 at 10:37 AM, Chiran Wijesekara <chir...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi all,
>>>>>>>
>>>>>>> we have decided to create a REST endpoint for the purpose of claim
>>>>&
- page 10 - https://go.forrester.com/wp-content/uploads/Forrester-
> 2018-Predictions.pdf
>
>
> Regards,
> Chamila de Alwis
> Committer and PMC Member - Apache Stratos
> Associate Technical Lead | WSO2
> +94 77 220 7163 <077%20220%207163>
> Blog: https://medium.com/@ch
Has ability to delete/update Apps shared with
>>> them. The reason for this is to address practical issues that take place
>>> when the App owner leaves an organization and there needs to be some way to
>>> delete/update such an Application.
>>>
>>
>> +
Sanjeewa,
>
> On Tue, Feb 6, 2018 at 12:33 PM, Sanjeewa Malalgoda <sanje...@wso2.com>
> wrote:
>
>>
>>
>> On Mon, Feb 5, 2018 at 11:29 PM, Ishara Karunarathna <isha...@wso2.com>
>> wrote:
>>
>>> HI Sanjeewa,
>>>
>>> Pseu
ide other organizational rules. So if a particular organization has
>> a policy to retain user data for 6 months and the user has consented to
>> that, the user only has the "right to be forgotten" after the 6 months has
>> passed. Until then the organization has the
IAM feature list of APIM.
>>
>> WDYT ?
>>
>> Thanks,
>> Asela.
>>
>> --
>> Thanks & Regards,
>> Asela
>>
>> ATL
>> Mobile : +94 777 625 933 <+94%2077%20762%205933>
>> +358 449 228 979
>>
of flexibility not needed at all?
>
>
>
> On Fri, Feb 2, 2018 at 11:11 AM, Sanjeewa Malalgoda <sanje...@wso2.com>
> wrote:
>
>> Nuwan, All,
>> When we are calling with external systems such as scim we will use user
>> ID. But internal flow manly goe
anks and Regards
>
> On Thu, Feb 1, 2018 at 6:05 PM, Sanjeewa Malalgoda <sanje...@wso2.com>
> wrote:
>
>> Hi All,
>> Recently we evaluated GDPR requirement(right to be forgotten) for API
>> Manager 3.0.0 development. Our primary focus was to find a way to implemen
gt; such as inability to change a username, problems with the same user in
>> different cases, etc. Meaning that APIM v3 was already GDPR compliant in
>> that sense. It we now have to build an addition layer to make the code GDPR
>> compliant, we've basically lost our design obj
ge a username, problems with the same user in
>> different cases, etc. Meaning that APIM v3 was already GDPR compliant in
>> that sense. It we now have to build an addition layer to make the code GDPR
>> compliant, we've basically lost our design objective of using user ids
>> inste
to do same for light weight auth framework as well.
I would like to know others opinion on this before move forward.
Thanks,
sanjeewa.
--
*Sanjeewa Malalgoda*
WSO2 Inc.
Mobile : +94713068779
<http://sanjeewamalalgoda.blogspot.com/>blog
:http://sanjeewamalalgoda.blo
ile
>>>>>>>>>> updating API
>>>>>>>>>>source via Swagger Editor in API Publisher.
>>>>>>>>>>5. Swagger UI in APIM 2.2.0 has been upgraded to 3.x version
>>>>>>>>>>so that
p -f qa/sampleApp.zip --preserveOwner
>>>>>> --addSubscriptions -e prod
>>>>>>
>>>>>>
>>>>>>
>>>>>> <https://github.com/randilu/WatchOver/new/master?
le : +94 76 667 8752 <+94%2076%20667%208752>
>> Web : http://wso2.com
>> <http://wso2.com/signature>
>>
>
>
>
> --
> *Renuka Fernando*
> Software Engineering Intern | WSO2 Inc
>
> Email : r
n the timeout
>>>> configuration.
>>>>
>>>> 4. *Include an ‘Age’ header with the response*
>>>> Cache mediator should return the true TTL value of a response without
>>>> altering the value of the cache-control ma
ts define proper response codes as well(201 to created, 202 accepted
etc).
What is the plan to expose this API to outside? Is it MSF4J? If that is the
case you can start with swagger definition and move forward.
Thanks,
sanjeewa.
>> Regards,
>> Asitha
>>
>> --
>> *Asith
carbon-auth
>>> APIs and intercepts requests and applies permission checks.
>>>- Keeping the security interceptor at the product level so each
>>>product can implement their own security interceptor.
>>>
>>> Thanks!
>>>
>>>
>&
identity server team had experiences with this API they can provide
suggestions for API and implementation. We will expose this as MSF4J based
API from carbon auth run time.
Lets use this thread to discuss all aspects of scope registration and
finalize implementation.
Thanks,
sanjeewa.
--
*Sanjeewa
budu Gunatilaka*
>> Committer and PMC Member - Apache Stratos
>> Senior Software Engineer
>> WSO2, Inc.: http://wso2.com
>> mobile : +94774078049 <%2B94772207163>
>>
>>
>
>
> --
> Susankha Nirmala
> Senior Software Engineer
> WSO2, Inc.: http://wso2.com
&
unning requests etc (and there are more
>>>>> techniques). Thus, caching, concurrency control etc is an aspect of Level
>>>>> 2. And we strive towards Level 2 support.
>>>>>
>>>>> But this does not imply that each of our products are
t;>>>>
>>>>> [1] https://github.com/wso2/carbon-apimgt/issues/4690
>>>>> [2] https://github.com/wso2/carbon-apimgt/pull/4679
>>>>>
>>>>>
>>>>> Appreciate any suggestions.
>>>>> Than
512>
>>> WSO2, Inc. | http://wso2.com/
>>> Lean . Enterprise . Middleware
>>>
>>> ___
>>> Architecture mailing list
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/lis
?
>
If we have federated users then anyway we might need to use extension for
do certain things. Yes in APIM 3Xx we will not remove any of the existing
capabilities. And we will specifically check federated user scenario.
Thanks,
sanjeewa.
>
> Regards,
> Johann.
>
> On Mon, O
ny authentication mechanism.
Thanks,
sanjeewa.
>
>
>
>
> More information on the solution can be found at [1]
>
>
> [1] https://docs.google.com/a/wso2.com/document/d/1vFP_GZcuLzJrk
> RDV3mCfuSDkwC8eKClmp4zt-lUs1Ro/edit?usp=sharing
>
> --
> Best Regards,
> *Nivea
user
present in user store connected. So if its federated user then populate
standard claims will be failed and we need to handle it.
Thanks,
sanjeewa.
>
> Thanks & Regards,
> Johann.
>
> --
>
> *Johann Dilantha Nallathamby*
> Senior Lead Solutions Engineer
> WSO2, Inc.
&
;>>>
>>>>>> ___
>>>>>> Architecture mailing list
>>>>>> Architecture@wso2.org
>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>&
PereraWSO2 <https://www.google.com/+IsuruPereraWSO2/about>
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
s this something we see valuable that can be added to IS 5.4.0 or 5.5.0?
>
> [1] https://wso2.org/jira/browse/IDENTITY-1131
> [2] https://github.com/wso2/carbon-identity/pull/1511
>
> Thanks & Regards,
> Johann.
>
> --
>
> *Johann Dilantha Nallathamby*
> Senio
a
>
> ATL
> Mobile : +94 777 625 933 <077%20762%205933>
> +358 449 228 979
>
> http://soasecurity.org/
> http://xacmlinfo.org/
>
--
*Sanjeewa Malalgoda*
WSO2 Inc.
Mobile : +94713068779
<http://sanjeewamalalgoda.blogspot.com/>blog
:htt
g All User Supplied Input
>>
>>
>>
>> Design Details
>>
>> Number of User Interfaces is going to be added to the API Manager as
>> admin users should have a way to enable/disable/create threat protection
>> policies.
>>
>> Threat prot
On Tue, Aug 1, 2017 at 6:12 AM, Isuru Haththotuwa <isu...@wso2.com> wrote:
> On Mon, Jul 31, 2017 at 2:51 PM, Sanjeewa Malalgoda <sanje...@wso2.com>
> wrote:
>
>>
>>
>> On Fri, Jul 28, 2017 at 1:12 PM, Sabeena Kumrawadu <sabe...@wso2.com>
>> w
nt for the design is much appreciated.
>
> Thank you,
> Best Regards.
>
> --
> *Sabeena Kumarawadu* | Software Engineering Intern
> WSO2 Lanka (Pvt) Ltd.
> #20, Palm Grove, Colombo 03, Sri Lanka
> Mobile: +94 71 0372856 <071%20037%202856>
&g
sses that extends
>>>>>> ABCRequestInterceptor
>>>>>>
>>>>>> But , we bind the interceptor as
>>>>>>
>>>>>> @RequestInterceptor(ABCRequestInterceptor.class)
>>>>>>
>>>>>
;> send necessary scopes in the beginning.
>>
>> And I have following questions regarding this.
>>
>> 1. How do you configure this IDPs other than WSO2 identity server
>> 2. How do you handle logout ?
>>
> I think we can revoke token when user logout happens.
Thank
..@wso2.com
> Mobile: 0719143658 <071%20914%203658>
> [image: http://wso2.com/signature] <http://wso2.com/signature>
>
--
*Sanjeewa Malalgoda*
WSO2 Inc.
Mobile : +94713068779
<http://sanjeewamalalgoda.blogspot.com/>blog
:http://sanjeewamalalgoda.blogspot.com/
<ht
>
> On Fri, May 19, 2017 at 6:37 PM, Sanjeewa Malalgoda <sanje...@wso2.com>
> wrote:
>
>> One other issue i see with ballerina editing or setting throttling tiers
>> is, business API owners need to handle that complexity.
>> Usually developers will deve
tensible API lifecycle states in c5 implementation?
>>>>> If we have any user who doesn't want this blocked state can remove from
>>>>> state configuration and who wants this blocked state can keep this state
>>>>> in
>>>>> configuration.
>>>
e comment
> permission to a moderator role(api owner or a configurable moderator role)?
>
> On Fri, May 19, 2017 at 11:22 AM, Sanjeewa Malalgoda <sanje...@wso2.com>
> wrote:
>
>> Can anyone point me any site/forum which allow you to edit others
>> comment(not appro
t;state" to the comment, need to implement a
> workflow, a callback mechanism, a workflow cleanup, etc. But if we just
> write a piece of code which allows a pre-configured role to remove, edit
> comments, I think the implementation is much simpler.
>
> On Fri, May 19, 2017 at 10:52 A
On Fri, May 19, 2017 at 10:43 AM, Bhathiya Jayasekara <bhath...@wso2.com>
wrote:
> Hi Sanjeewa,
>
> On Thu, May 18, 2017 at 5:09 PM, Sanjeewa Malalgoda <sanje...@wso2.com>
> wrote:
>
>> I don't think its worth to get complete permission model for comments as
>
gt;>>>>>>>>
>>>>>>>>>>> Or should we be doing an explicit permission validation? Do we
>>>>>>>>>>> have any drawbacks in doing this check?
>>>>>>>>>>>
>>>>>>>>>>>
1 - 100 of 231 matches
Mail list logo
