BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20140627T09Z
DTEND:20140627T10Z
DTSTAMP:20140624T065312Z
ORGANIZER;CN=Malintha Adikari:mailto:malin...@wso2.com
UID:s9dri4824nh5t46ruj75ngi...@google.com
Hi All,
Here is a brief update on implementation of blocking deactivated tenant
requests.
*Problem:*
Even if we deactivated tenant, still they can access services(APIs, proxy
etc) deployed in server. This will effect to multitenanted products.
*Suggested solution:*
Implement dispatcher and
We have another alternative to fix this problem. If you implement a handler
at the transport phase then you have to perform checks for each and every
request which would not be an elegant solution.
How about checking this during the tenant loading time. We simply do not
load the tenant if its
Again, in your proposed solution we load the tenant blindly without knowing
that its deactivated. This means all the tenant listeners are invoked, svn
depsync is triggered etc. If we simply stop loading the tenant, then none
of unnecessary tasks will get activated.
Thanks,
Sameera.
On Tue, Jun
Hi Rasika, are these the final set of methods? If not, can you pls publish
the final set?
Thanks
Shevan
On Tue, Jun 24, 2014 at 10:55 AM, Rasika Hettige rasi...@gmail.com wrote:
Hi All,
To further explain on why we have selected the following methods:
On Tue, Jun 24, 2014 at 4:21 PM, Sameera Jayasoma same...@wso2.com wrote:
We have another alternative to fix this problem. If you implement a
handler at the transport phase then you have to perform checks for each and
every request which would not be an elegant solution.
How about checking
Hi Shevan,
Please find the final method list below:
*deleteIdentity *- Deletes the specified identity (email address or domain)
from the list of verified identities.
*listIdentityDkimAttributes *- Takes a list of identities as input and
returns the current status of Easy DKIM signing for an
