___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Hi,
Here is the architecture of the XACML based scope validator.
After whether access token has expired, the scope of the token will be
validated using JDBCScopeValidator and XACMLScopeValidator.
The JDBCScopeValidator was already implemented. The XACMLScopeValidator
will create an XACML
Hi Asanka,
The required queue/binding/exchange related data will be loaded once the
previously passive node is notified of becoming the active node.
This is considering the possibility of inconsistencies in a continuous
sync, which could also require reloading on becoming the active node.
Thank
Hi,
*@Johann* Thank you for the information. I was able to extend the handler
and listen to password change events.
Now I am working on publishing data to IS Analytics using the
EventStreamService.
I will keep the thread updated.
Thank you!
Regards,
NadunD
On Wed, Jan 17, 2018 at 2:14 PM,
Hi Dimuthu,
> In the above case, in the session map what do you have? What we should be
> storing is the Session Id even though the log says ContextId. Should the
> log be modified?
>
> 1750291c-611b-4305-9fbc-40ba183d5878 -->
> *9b8245d49407465772c9d25fef729bef3d00f07902b1c9d74d7795074557351d
Hi Kanapriya,
In the above case, in the session map what do you have? What we should be
storing is the Session Id even though the log says ContextId. Should the
log be modified?
1750291c-611b-4305-9fbc-40ba183d5878 -->
*9b8245d49407465772c9d25fef729bef3d00f07902b1c9d74d7795074557351d *
Is it?