Now, I will ask you what is this interceptor doing ? There are other
means to implement a mechanism that manage authentication, through
Authenticators. But that is another discussion…
The interceptor I’m implementing is actually capturing LDAP
add/modify/delete commands and calls REST api to reflect the changes
in a different system which is kinda synced with LDAP. I looked at
AvlPartition.add/modify method as a possible candidate, but don’t feel
like it’s the right place, or is it?
If you are to call a REST api when a modification is made on the LDAP
serve,r I would suggest your interceptor to be the last one in the
interceptor chain: just before the modification hits the backend. Doing
so would eliminate any potential operation rejection by one of the
previous interceptors.
Typically, if the authz interceptor reject the modification, what's the
point of calling the REST api ? Unless you want to have a track of every
request the server receives, and then having your interceptor in first
position would make sense...
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
