Re: [Dev] [IAM]Implementing Eventing Mechanism in token/code insertion/deletion or revocation

On Tue, Jan 23, 2018 at 10:54 PM, Hasanthi Purnima Dissanayake < hasan...@wso2.com> wrote: > Hi All, > > Requirement : > We have a requirement to insert/update or delete a row from a db table > once access token or authorization code is generated, revoked, code or > token status changed or a

Re: [Dev] [IAM]Implementing Eventing Mechanism in token/code insertion/deletion or revocation

Hi Darshana, > Hi Hasanthi, > > On Tue, Jan 23, 2018 at 10:54 PM, Hasanthi Purnima Dissanayake < > hasan...@wso2.com> wrote: > >> Hi All, >> >> Requirement : >> We have a requirement to insert/update or delete a row from a db table >> once access token or authorization code is generated,

Re: [Dev] [IAM]Implementing Eventing Mechanism in token/code insertion/deletion or revocation

Hi Hasanthi, On Tue, Jan 23, 2018 at 10:54 PM, Hasanthi Purnima Dissanayake < hasan...@wso2.com> wrote: > Hi All, > > Requirement : > We have a requirement to insert/update or delete a row from a db table > once access token or authorization code is generated, revoked, code or > token status

[Dev] [IAM]Implementing Eventing Mechanism in token/code insertion/deletion or revocation

Hi All, Requirement : We have a requirement to insert/update or delete a row from a db table once access token or authorization code is generated, revoked, code or token status changed or a refresh token is issued. Without directly invoking the db, we thought of implementing events to trigger